1 |
On Wed, Jun 3, 2009 at 4:05 AM, Marijn Schouten (hkBst)<hkBst@g.o> wrote: |
2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
3 |
> Hash: SHA1 |
4 |
> |
5 |
> Alec Warner wrote: |
6 |
>> On Sun, May 31, 2009 at 4:21 AM, Marijn Schouten (hkBst) |
7 |
>> <hkBst@g.o> wrote: |
8 |
>> Duncan wrote: |
9 |
>>>>> Patrick Börjesson <psychotical@×××××××.com> posted |
10 |
>>>>> 20090529201741.GB11660@×××××.nexus, excerpted below, on Fri, 29 May 2009 |
11 |
>>>>> 22:17:41 +0200: |
12 |
>>>>> |
13 |
>>>>>> Why exactly would you want to use --oneshot for a "leaf package" that is |
14 |
>>>>>> not depended on by any other package in the world set? If spam IS |
15 |
>>>>>> depended on by any other package (recursively) in the world set, it will |
16 |
>>>>>> be pulled in by --complete-graph, but that's not the case here if i |
17 |
>>>>>> understand it correctly, thus it's a package that you explicitly wanted |
18 |
>>>>>> installed, thus it belongs in the world set, and you should thus not use |
19 |
>>>>>> --oneshot for it. |
20 |
>>>>> I use -1 by default, here (via scriptlet), mainly so I don't have to |
21 |
>>>>> worry about cluttering up my world file while emerging individual |
22 |
>>>>> packages, just as I always use -NuD with my @system and @world runs. |
23 |
>>>>> |
24 |
>>>>> But for leaf packages, it serves as a sort of test install as well. |
25 |
>>>>> Since I always do revdep-rebuild -p and emerge --depclean -p after every |
26 |
>>>>> update (typically 2-3 times a week), then rebuild and clean as I need to, |
27 |
>>>>> keeping the "trial merges" on the depclean list for a few days keeps me |
28 |
>>>>> aware of them. If I know it's something I want to keep, I run a |
29 |
>>>>> different scriptlet without the -1, but that's not often once a system is |
30 |
>>>>> up and running with the normal working set merged. Meanwhile, I |
31 |
>>>>> ultimately either emerge -C (or let depclean handle it) the "trialware", |
32 |
>>>>> or emerge --noreplace, thus adding it to world. |
33 |
>>>>> |
34 |
>>>>> But experimental installs and their deps typically sit in the --depclean |
35 |
>>>>> list for anything from a few minutes to a few days, until I decide |
36 |
>>>>> whether I want to keep or remove them. |
37 |
>>>>> |
38 |
>>>>> If he was testing how the switches under discussion here worked and has a |
39 |
>>>>> similar policy, I could easily see him using -1 by habit, even if he |
40 |
>>>>> didn't explicitly reason that it was a test and therefore something he |
41 |
>>>>> didn't want in @world. |
42 |
>> I think this is an interesting use-case. It would be very simple to handle it by |
43 |
>> introducing an additional file that the package manager would use to record the |
44 |
>> packages that are installed on trial-basis. This would make it possible to |
45 |
>> include these packages in dep-calculations, while still distinguishing them from |
46 |
>> packages that are in @world. Of course you can also fake it by creating a local |
47 |
>> virtual/trialware package (or possibly a @trialware group) of which you edit the |
48 |
>> deps, but this would be less convenient. For my personal workflow using -1 for |
49 |
>> trials is working well enough, atm. |
50 |
>> |
51 |
>>> Why is a custom set less convenient? |
52 |
> |
53 |
> Well, instead of "emerge --trialware package" you would first have to edit your |
54 |
> @trialware set and then "emerge @trialware". The same goes for when you want to |
55 |
> remove some trialware. |
56 |
> Perhaps some generalization of --trialware along the lines of |
57 |
> - --add-to-set=trialware could be fleshed out as a useful extension of portage. |
58 |
|
59 |
I like sandwiches too, so perhaps we can have a |
60 |
--sudo_make_me_a_sandwich option to emerge? |
61 |
|
62 |
But seriously, this is linux. If users want do deal with "a set of |
63 |
packages that are like trialware" then they should use the sets |
64 |
functionality that emerge already ships with. emerge |
65 |
--add-to-set=blah might be passable but IMSHO emerge has plenty of |
66 |
options already and users can easy write their own wrappers for this |
67 |
kind of thing. Emerge doesn't need every tiny feature built into it. |
68 |
|
69 |
> |
70 |
> Marijn |
71 |
> |
72 |
> - -- |
73 |
> If you cannot read my mind, then listen to what I say. |
74 |
> |
75 |
> Marijn Schouten (hkBst), Gentoo Lisp project, Gentoo ML |
76 |
> <http://www.gentoo.org/proj/en/lisp/>, #gentoo-{lisp,ml} on FreeNode |
77 |
> -----BEGIN PGP SIGNATURE----- |
78 |
> Version: GnuPG v2.0.11 (GNU/Linux) |
79 |
> Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org |
80 |
> |
81 |
> iEYEARECAAYFAkomWO8ACgkQp/VmCx0OL2wGHACfdlOdzvfLM3aUafiuOVQTlRnz |
82 |
> vvMAoMMeLUxnM2i8fpJhClxbsIqwMf3Z |
83 |
> =HSIG |
84 |
> -----END PGP SIGNATURE----- |
85 |
> |
86 |
> |