| 1 |
Okay. Understood! |
| 2 |
I would like to have a look in how an ebuild is constructed. |
| 3 |
I figured out how to create an rpm and now want to know how it looks like for |
| 4 |
an ebuild. |
| 5 |
I didn't receive the actual Mail of Nick. |
| 6 |
Can you send it to me again? Or can I download it from the gentoo project |
| 7 |
homepage? |
| 8 |
|
| 9 |
Am Donnerstag, 25. August 2005 22:50 schrieb Alec Shaner: |
| 10 |
> Markus Döbele wrote: |
| 11 |
> > Can't the rest be automated too? |
| 12 |
> > I mean creating the directories |
| 13 |
> > and to check first if portage is installed? |
| 14 |
> > Would be easier for the users. |
| 15 |
> > |
| 16 |
> > Then a link should be created in PATH thet you can type laby everywhere. |
| 17 |
> |
| 18 |
> Once the ebuild is officially in the portage tree, it is all automated, |
| 19 |
> i.e., to install and run your program would be as simple as this: |
| 20 |
> |
| 21 |
> # emerge laby |
| 22 |
> # laby |
| 23 |
> |
| 24 |
> All the steps that I followed from Nick Rout were part of using/testing |
| 25 |
> an unofficial ebuild. Not having portage installed is akin to not having |
| 26 |
> rpm installed on RedHat. |
| 27 |
|
| 28 |
-- |
| 29 |
gentoo-user@g.o mailing list |
Archives