In the past I revised the ebuild for Opera a couple of times to get all the versions correctly mangled to fit the paths Opera Inc likes to use. I have now used versionator.eclass to rewrite the ebuilds so that they use PV instead of harcoded path segments. Naturally, the official release date then becomes part of PV... Two ebuilds to follow: one for a regular release and one (different format) for Opera's previews. Maybe at one point I will write a single ebuild template that handles both regular releases and previews as well as beta releases.
Created attachment 73458 [details] opera-8.51.20051114.ebuild
Created attachment 73459 [details] opera-9.0.20051020_pre1.ebuild
In both ebuilds I left RESTRICT="nomirror" to aid in testing them...
I thin the release date shouldn't be included in the official version since it isn't interesting to the end user. Also it doesn't make a difference if you specify the date in the ebuild name or in the ebuild itself.But in the end I don't really care, it's nothing really important.
Created attachment 73503 [details, diff] opera-8.51-versionator.patch Dev-friendly patch for opera-8.51.ebuild
Created attachment 73505 [details, diff] opera-8.51-versionator.patch Dev-friendly patch for opera-8.51.ebuild
Comment on attachment 73505 [details, diff] opera-8.51-versionator.patch Sorry for the bugspam.
sorry, for me they are not really more maintainer-friendly. changing two lines in the ebuild is not to much i think and the release date shouldn't be included in the ebuildname, so for now i close this as wontfi
