| 1 |
On Thu, 2004-04-29 at 22:36, Nick Rout wrote: |
| 2 |
> On Thu, 29 Apr 2004 17:32:04 -0400 (EDT) |
| 3 |
> Ajai Khattri <ajai@××××.net> wrote: |
| 4 |
> |
| 5 |
> > On Fri, 30 Apr 2004, Eldad Zack wrote: |
| 6 |
> > |
| 7 |
> > > The best way is to allow run-time configuration in /etc files. |
| 8 |
> > |
| 9 |
> > I had a feeling that would be the answer ;-) |
| 10 |
> > |
| 11 |
> > So I have some more work to do I guess. |
| 12 |
> > |
| 13 |
> |
| 14 |
> some ebuilds tell you to run a configuration script after the ebuild |
| 15 |
> completes (although often this disappears in the other cruft that emerge |
| 16 |
> throws past you) |
| 17 |
> |
| 18 |
> something like |
| 19 |
> |
| 20 |
> ebuild /usr/portage/path-to/app/app-1.0.ebuild configure |
| 21 |
> |
| 22 |
> (although thats probably not the wording. I cannot be darned finding a |
| 23 |
> live example now.) |
| 24 |
> |
| 25 |
|
| 26 |
Since I have just 10 minutes ago emerged it, freenet does this. |
Archives