| 1 |
yes well when it is in portage the file will be updated into the portage |
| 2 |
tree automatically. in the meantime you have to download both the ebuild |
| 3 |
and the wrapper script, same as for any other new ebuild. Sorry if I |
| 4 |
didn't make this clear in the email with the new ebuild. |
| 5 |
|
| 6 |
I don't think its correct for an ebuild to create a script on the fly, |
| 7 |
ie embedded in the ebuild itself. |
| 8 |
|
| 9 |
|
| 10 |
FYI I have found a "games ebuild howto" which may lead me to change how |
| 11 |
the ebuild works before committing it to bugzilla and the terrible and |
| 12 |
swift swords of the devs... |
| 13 |
|
| 14 |
For example i stored the highscores.dat file (which needs to be writable) |
| 15 |
in /usr, whereas you shouldn't have programs writing to /usr, so it |
| 16 |
should go in /var somewhere. |
| 17 |
|
| 18 |
|
| 19 |
On Mon, 29 Aug 2005 12:47:02 -0700 |
| 20 |
Greg Bengeult wrote: |
| 21 |
|
| 22 |
> |
| 23 |
> Nick Rout wrote: |
| 24 |
> |
| 25 |
> >did you have the laby wrapper script |
| 26 |
> >in /usr/local/portage/games-roguelike/laby/files ?? |
| 27 |
> > |
| 28 |
> >I posted the wrapper script with the first version of the ebuild. |
| 29 |
> > |
| 30 |
> > |
| 31 |
> > |
| 32 |
> > |
| 33 |
> Nope, I didn't keep a copy of it at the time. To be considered |
| 34 |
> complete, the ebuild should either include a copy of the wrapper or |
| 35 |
> should create it on the fly. The user shouldn't have to do anything |
| 36 |
> more than "emerge laby". |
| 37 |
> |
| 38 |
> -- |
| 39 |
> gentoo-user@g.o mailing list |
| 40 |
|
| 41 |
-- |
| 42 |
Nick Rout <nick@×××××××.nz> |
| 43 |
|
| 44 |
-- |
| 45 |
gentoo-user@g.o mailing list |
Archives