1 |
maillog: 13/01/2007-02:05:45(+0100): Harald van Dijk types |
2 |
> On Fri, Jan 12, 2007 at 07:12:00PM +0000, Ciaran McCreesh wrote: |
3 |
> > On Fri, 12 Jan 2007 18:42:20 +0100 Harald van Dijk <truedfx@g.o> |
4 |
> > | With ACCEPT_RESTRICT=-fetch, you tell it you don't want packages with |
5 |
> > | RESTRICT=fetch, so portage /should/ complain regardless of whether the |
6 |
> > | sources are available. |
7 |
> > |
8 |
> > Which is my point -- that's a stupid thing to request. A sensible thing |
9 |
> > to request would be "mask anything that will require me to fetch |
10 |
> > something manually". |
11 |
> |
12 |
> It's not a stupid thing to request to install only packages that allow |
13 |
> you to emerge -e world if / gets corrupted. |
14 |
|
15 |
Consider how portage shows an indication in the --pretend (or --ask) |
16 |
output if a package requires manual fetching or if the download is |
17 |
already done. You know that you have to either fetch the files or avoid |
18 |
the package. With ACCEPT_RESTRICT=fetch it would have failed anyway. |
19 |
|
20 |
Something similar could be done about userpriv. Another red letter |
21 |
indicating that a package will compile as root (and the user is free to |
22 |
go ahead or abort as they see fit). The letter can be green if userpriv |
23 |
is not in FEATURES. |
24 |
|
25 |
The problem I am having with RESTRICT=userpriv is that it is *silent* |
26 |
about what it does. If there were some indication I would have been |
27 |
happy. Anyone else feel the same way? |
28 |
|
29 |
-- |
30 |
(* Georgi Georgiev (* Mal: "I, uh, better go see how the (* |
31 |
*) chutz@×××.net *) inevitable mutiny is coming along..." *) |
32 |
(* http://www.gg3.net/ (* (* |
33 |
-- |
34 |
gentoo-dev@g.o mailing list |