| 1 |
Okay, but this means to me that it makes no real difference if I upload it to |
| 2 |
2 destinations all the time. |
| 3 |
I am living in Argentina and my internet connection here is very slow :-( |
| 4 |
|
| 5 |
When we have to write a special file (ebuild) anyway so I would suggest to |
| 6 |
rename the funny name the server is giving us. |
| 7 |
We just have to insert a variable which contains the actual version. |
| 8 |
|
| 9 |
Saves me a lot of time. |
| 10 |
And I want to concentrate my efforts on making laby better and not other |
| 11 |
stuff. |
| 12 |
|
| 13 |
There is still a lot to to. And I want to beat the Windows version as soon as |
| 14 |
possible! |
| 15 |
|
| 16 |
|
| 17 |
Am Mittwoch, 24. August 2005 03:58 schrieb Nick Rout: |
| 18 |
> On Tue, 23 Aug 2005 23:48:45 +0200 |
| 19 |
> |
| 20 |
> Markus Döbele wrote: |
| 21 |
> > Okay, then lets use sourceforge. |
| 22 |
> > I will release a new version tonight! Will be 1.0.2. |
| 23 |
> > |
| 24 |
> > (Integrated 10 new magical items, The special levels look really nice now |
| 25 |
> > and I included a new one: underground forest. The dragon room is new. And |
| 26 |
> > we got a room for trainers now :-) ) |
| 27 |
> > |
| 28 |
> > How do we handle it with sourceforge that we always get the newest |
| 29 |
> > version? Do I have to edit the same release all the time. Or is there a |
| 30 |
> > mechanism that gets the neweset file automatically? |
| 31 |
> |
| 32 |
> The versioning is handled like this: |
| 33 |
> |
| 34 |
> each ebuild has a name and version in it. I would call the current laby |
| 35 |
> ebuild laby-1.0.1.ebuild and it would include a line like: |
| 36 |
> |
| 37 |
> SRC_URI="mirror://sourceforge/synce/${P}.tar.gz" |
| 38 |
> |
| 39 |
> ${P} includes the version number automatically. |
| 40 |
> |
| 41 |
> When a new version is released someone needs to write a new ebuild, but |
| 42 |
> as all versioning is handled automatically, this is usually just a |
| 43 |
> matter of copying the previous one and renaming it to e.g. |
| 44 |
> laby-1.0.2.ebuild. |
| 45 |
> |
| 46 |
> portage picks up the new version number from the filename and adjusts |
| 47 |
> the download URL by virtue of the ${P} variable. |
| 48 |
> |
| 49 |
> It does rely on you keeping the filenaming consistent and not suddenly |
| 50 |
> changing from laby-1.0.1.tar.gz to lostlabyrinth-1.0.2.tgz. |
| 51 |
> |
| 52 |
> For more info see |
| 53 |
> |
| 54 |
> http://www.gentoo.org/proj/en/devrel/handbook/handbook.xml?part=2&chap=1 |
| 55 |
> |
| 56 |
> |
| 57 |
> -- |
| 58 |
> Nick Rout <nick@×××××××.nz> |
| 59 |
|
| 60 |
-- |
| 61 |
gentoo-user@g.o mailing list |
Archives