| 1 |
On Mon, 2005-10-03 at 19:39 +0200, Jan Kundrát wrote: |
| 2 |
> Ciaran McCreesh wrote: |
| 3 |
> > On Mon, 3 Oct 2005 23:15:37 +0900 Georgi Georgiev <chutz@×××.net> wrote: |
| 4 |
> > | Does it seem like it is time for RESTRICT=interactive. Such ebuilds |
| 5 |
> > | would refuse to emerge if stdout is not a tty. If only there was |
| 6 |
> > | use-flag based RESTRICT... |
| 7 |
> > |
| 8 |
> > No, because then that would encourage even more people to abuse the |
| 9 |
> > system and write incorrect ebuilds. |
| 10 |
> |
| 11 |
> IMHO this could be enforced by some policy ("don't use |
| 12 |
> RESTRICT=interactive unless you really need it and some_group has given |
| 13 |
> you the ok")... |
| 14 |
No, it shouldn't. interactive ebuilds make remote updating very |
| 15 |
time-consuming (you have to check wether it wants you to interact with i |
| 16 |
or not yet) and are usually not needed - just ask the user to run ebuild |
| 17 |
foo config (or whatever does thw job) manually. |
| 18 |
-- |
| 19 |
Stand still, and let the rest of the universe move |
Archives