On Tue, 23 Aug 2005 23:48:45 +0200
Markus Döbele wrote:
> Okay, then lets use sourceforge.
> I will release a new version tonight! Will be 1.0.2.
>
> (Integrated 10 new magical items, The special levels look really nice now and
> I included a new one: underground forest. The dragon room is new. And we got
> a room for trainers now :-) )
>
> How do we handle it with sourceforge that we always get the newest version?
> Do I have to edit the same release all the time. Or is there a mechanism that
> gets the neweset file automatically?
The versioning is handled like this:
each ebuild has a name and version in it. I would call the current laby
ebuild laby-1.0.1.ebuild and it would include a line like:
SRC_URI="mirror://sourceforge/synce/${P}.tar.gz"
${P} includes the version number automatically.
When a new version is released someone needs to write a new ebuild, but
as all versioning is handled automatically, this is usually just a
matter of copying the previous one and renaming it to e.g.
laby-1.0.2.ebuild.
portage picks up the new version number from the filename and adjusts
the download URL by virtue of the ${P} variable.
It does rely on you keeping the filenaming consistent and not suddenly
changing from laby-1.0.1.tar.gz to lostlabyrinth-1.0.2.tgz.
For more info see
http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1
--
Nick Rout <[EMAIL PROTECTED]>
--
[email protected] mailing list
