It doesn't look up to date to me. As http://www.opera.com/browser/download/
will tell you the current stable version of Opera is 11.11. And as the changelog for this build states http://www.opera.com/docs/changelogs/unix/1111/
"Opera 11.11 is a recommended upgrade offering security and stability enhancements." (security issues are listed at the end of each changelog entry).
We only maintain a single stable version, hence all Opera users should be running Opera 11.11 (or one of our 11.50 development builds) to be secure. However, looking at the following pages:http://download.salixos.org/i486/13.1/source/xap/opera/http://download.salixos.org/i486/13.37/ ... xap/opera/http://download.salixos.org/i486/curren ... xap/opera/
I only see SLKBUILDs for Opera 11.01 (for Salix 13.1) and Opera 11.10 (for Salix 13.37), i.e. there is no stable and secure version of Opera for any recent version of Salix, within the Salix source repositories.
I also note that all three SLKBUILDs do indeed use the tar package as a source, whilst laci had stated that when you use 'slapt-src', an rpm is used.
(I'll speculate the next bit because I don't have a copy of Salix to hand to check, please correct me if I am wrong)
I assume that slapt-src, will use SalixOS sources or SlackBuilds.org and hence the version being built is from the the SlackBuilds repository, which uses the Opera rpm files. If so I can see how this will work for Slackware users but not Salix users. The reason being is that the 'recommended method of install for Slackware is a full install (which includes rpm), whilst the Salix default installs do not include rpm.
Is it enough that I submit an updated SLKBUILD for inclusion in Salix? By that I mean if I provide one will slapt-src favour the Salix source repository over SlackBuilds repository?
Also do I submit this once for 13.37 or three times, once for 13.1, once for 13.37 and once for current? If you intend for them to all be supported and hence secure?