| 1 |
On Saturday 01 May 2004 21:52, Jeremy Maitin-Shepard wrote: |
| 2 |
> Paul de Vrieze <pauldv@g.o> writes: |
| 3 |
> > [snip] |
| 4 |
> > |
| 5 |
> >> Like I said, it would only have to ask for information that wasn't |
| 6 |
> >> available from the cache of answers. Provided there was a tool to |
| 7 |
> >> pre-edit the cache - something I suggested earlier - then your scenarios |
| 8 |
> >> would work. |
| 9 |
> > |
| 10 |
> > I agree with such a setup. Have a way in which - optionally - the ebuild |
| 11 |
> > can be preconfigured. This configuration would need to be selfcontained |
| 12 |
> > in such a way that the configuration files can be copied and created at |
| 13 |
> > any time. |
| 14 |
> |
| 15 |
> I much prefer requiring pre-configuration. I don't like the idea of |
| 16 |
> emerge being interactive under any circumstance. |
| 17 |
|
| 18 |
The optional (for the user, not the ebuild developer) configuration would |
| 19 |
happen before anything is downloaded, unpacked or compiled. Alternatively it |
| 20 |
should be possible to do this for a lot of hosts at the same time and just |
| 21 |
copy the configuration file(s) like what is possible with package.use |
| 22 |
|
| 23 |
Paul |
| 24 |
|
| 25 |
-- |
| 26 |
Paul de Vrieze |
| 27 |
Gentoo Developer |
| 28 |
Mail: pauldv@g.o |
| 29 |
Homepage: http://www.devrieze.net |
Archives