Right Markus I have written an ebuild that installs the package and it works, although I am not sure if its how a pro would have done it.
It downloads the compiled version 1.0.0 from sourceforge (can't test it on 1.0.1 or 1.0.2 until you put them on sourceforge.) Once you have done that, and I have tested it, I'll make it available for others to test. Basically it downloads the compiled tarball and installs the executable (laby) and the support files (sounds.pak, highscores.dat, graphics.pak) to /usr/lib/laby/ It puts a script into /usr/games/bin. The script simple cd's to /usr/lib/laby and them executes laby. (It seems to need to be executed from the same directory the support files are in, makes sense really) Comments on my chosen file locations would be appreciated. They are easy enough to change. It also installs the readme.txt to /usr/share/doc/laby-1.0.0 (this is a gentoo standard location for documentation). If people think I should it can also put readme_waffen.txt and readme_zauber.txt into the same place, but as I don't know german i am unsure if they are really helpful, or just take up space :-) On Wed, 2005-08-24 at 20:49 +1200, Nick Rout wrote: > Markus, you just keep working on the program and make sure you upload it > to sourceforge, I'll do the ebuilds :-) > > On Wed, 2005-08-24 at 10:06 +0200, Markus Döbele wrote: > > Okay, but this means to me that it makes no real difference if I upload it > > to > > 2 destinations all the time. > > I am living in Argentina and my internet connection here is very slow :-( > > > > When we have to write a special file (ebuild) anyway so I would suggest to > > rename the funny name the server is giving us. > > We just have to insert a variable which contains the actual version. > > > > Saves me a lot of time. > > And I want to concentrate my efforts on making laby better and not other > > stuff. > > > > There is still a lot to to. And I want to beat the Windows version as soon > > as > > possible! > > -- > Nick Rout <[EMAIL PROTECTED]> > -- Nick Rout <[EMAIL PROTECTED]> -- [email protected] mailing list
