On 09/11/13 12:03, Eduardo Lima (Etrunko) wrote: > 2013/9/11 Bertrand Jacquin <be...@meleeweb.net>: > > Hi, > > > > On 2013-09-11 00:36, Eduardo Lima (Etrunko) wrote: > >> We now have tarballs up for testing in under the new pre-releases > >> directory: > >> > >> http://download.enlightenment.org/pre-releases/efl-1.7.9/ > >> http://download.enlightenment.org/pre-releases/enlightenment-0.17.5/ > > > > IMHO, it's bad to name tarball 'e_dbus-1.7.9.tar.bz2' (here for e_dbus > > exemple). Think about google bot and other crawlers that will put in the > > first result 'e_dbus-1.7.9.tar.bz2' corresponding to the pre-release > > directory, and this even when release will happenning, people will not > > see pre-releases subdirectory at first. > > > > Also, it may lead to misunderstood from people that will already have a > > file named e_dbus-1.7.9.tar.bz2 in their directory. > > > > Naming them e_dbus-1.7.9_pre1.Tar.bz2 in preferable or anything else > > that is not the final tarball name. > > > > It is already enough work to update configure.ac, ChangeLogs and NEWS > for all 17 packages we ship, and I for myself am not doing it all over > again only to remove a 'pre' tag. The idea is to move the tarballs to > the release directory and remove the pre-release one whenever the > packages are tested and good to go.
You don't have to change the configure.ac and friends, just rename the final tarball. You see, last time for 1.7.8, there was problem to fix so new packages were uploaded again with the exact same name. I, myself, couldn't figure which one of the tarballs were patched as they got all the same timestamp. I do believe that different code tarballs should have different names. If it's too difficult, at least give some checksums of the final tarballs so people could check what they have without downloading them all over again. -- Jérôme Pinot http://ngc891.blogdns.net/
signature.asc
Description: Digital signature
------------------------------------------------------------------------------ How ServiceNow helps IT people transform IT departments: 1. Consolidate legacy IT systems to a single system of record for IT 2. Standardize and globalize service processes across IT 3. Implement zero-touch automation to replace manual, redundant tasks http://pubads.g.doubleclick.net/gampad/clk?id=51271111&iu=/4140/ostg.clktrk
_______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
