| 1 |
I know I should upload this to bugs.gentoo.org, but as we are in the |
| 2 |
middle of a thread i thought I'd load it here for anyone interested to |
| 3 |
try (and to criticise) |
| 4 |
|
| 5 |
Please be gentle with me, this is my first ebuild. |
| 6 |
|
| 7 |
The ebuild is attached, as is the small startup script. The way it works |
| 8 |
and installs is detailed below (although the version is now 1.0.2 rather |
| 9 |
than 1.0.0) |
| 10 |
|
| 11 |
You need to have portage overlay enabled, and assuming your overlay is |
| 12 |
in /usr/local/portage, you need to make the following directories: |
| 13 |
|
| 14 |
/usr/local/portage/games-roguelike/laby/ |
| 15 |
and |
| 16 |
/usr/local/portage/games-roguelike/laby/files |
| 17 |
|
| 18 |
the ebuild file goes in the former, the file laby goes in the latter. |
| 19 |
|
| 20 |
You will need to: |
| 21 |
|
| 22 |
ebuild /usr/local/portage/games-roguelike/laby/laby-1.0.2.ebuild digest |
| 23 |
|
| 24 |
and then add laby your list of unstable builds: |
| 25 |
|
| 26 |
echo "games-roguelike/laby ~x86" >> /etc/portage/package.keywords |
| 27 |
|
| 28 |
It _should_ then emerge fine. |
| 29 |
|
| 30 |
As long as you are in the games group you should be able to just run |
| 31 |
|
| 32 |
laby |
| 33 |
|
| 34 |
TODO: |
| 35 |
|
| 36 |
1. tidy up ownership and permissions of installed files. |
| 37 |
2. make the wrapper script stop artsd and restart it IF it was running |
| 38 |
in the first place. (alternatively run the program with artsdsp if arts |
| 39 |
is running? - thats probably a better option!) |
| 40 |
|
| 41 |
|
| 42 |
|
| 43 |
|
| 44 |
On Wed, 24 Aug 2005 22:42:16 +0200 |
| 45 |
Markus Döbele wrote: |
| 46 |
|
| 47 |
> Okay, I just uploaded the new release to sourceforge. |
| 48 |
> Its version 1.0.2 |
| 49 |
> |
| 50 |
> > Right Markus I have written an ebuild that installs the package and it |
| 51 |
> > works, although I am not sure if its how a pro would have done it. |
| 52 |
> > |
| 53 |
> > It downloads the compiled version 1.0.0 from sourceforge (can't test it |
| 54 |
> > on 1.0.1 or 1.0.2 until you put them on sourceforge.) Once you have done |
| 55 |
> > that, and I have tested it, I'll make it available for others to test. |
| 56 |
> > |
| 57 |
> > Basically it downloads the compiled tarball and installs the executable |
| 58 |
> > (laby) and the support files (sounds.pak, highscores.dat, graphics.pak) |
| 59 |
> > to /usr/lib/laby/ It puts a script into /usr/games/bin. The script |
| 60 |
> > simple cd's to /usr/lib/laby and them executes laby. (It seems to need |
| 61 |
> > to be executed from the same directory the support files are in, makes |
| 62 |
> > sense really) |
| 63 |
> > |
| 64 |
> > Comments on my chosen file locations would be appreciated. They are easy |
| 65 |
> > enough to change. |
| 66 |
> > |
| 67 |
> > It also installs the readme.txt to /usr/share/doc/laby-1.0.0 (this is a |
| 68 |
> > gentoo standard location for documentation). If people think I should it |
| 69 |
> > can also put readme_waffen.txt and readme_zauber.txt into the same |
| 70 |
> > place, but as I don't know german i am unsure if they are really |
| 71 |
> > helpful, or just take up space :-) |
| 72 |
> > |
| 73 |
|
| 74 |
-- |
| 75 |
Nick Rout <nick@×××××××.nz> |
Archives