1 |
On Mon, Jan 2, 2012 at 6:33 PM, Alan McKinnon <alan.mckinnon@×××××.com> wrote: |
2 |
> On Mon, 2 Jan 2012 11:20:19 -0500 |
3 |
> Michael Mol <mikemol@×××××.com> wrote: |
4 |
> |
5 |
>> On Mon, Jan 2, 2012 at 11:16 AM, Michael Mol <mikemol@×××××.com> |
6 |
>> wrote: |
7 |
>> > On Mon, Jan 2, 2012 at 11:09 AM, Michael Orlitzky |
8 |
>> > <michael@××××××××.com> wrote: |
9 |
>> >> On 01/02/2012 11:01 AM, Mark Knecht wrote: |
10 |
>> >>> |
11 |
>> >>> |
12 |
>> >>> I tell by knowing which files I want in @world. Everything in |
13 |
>> >>> world should be a package __I__ specifically want to use. |
14 |
>> >>> Everything in world (on my machines anyway) is something: |
15 |
>> >>> |
16 |
>> >>> 1) I'd call from the command line |
17 |
>> >>> 2) Need to write a little software myself, most specifically a |
18 |
>> >>> library 3) Aid in displaying things, like font packages |
19 |
>> >>> 4) Something required by Gentoo that I don't totally understand, |
20 |
>> >>> like a virtual package. |
21 |
>> >>> |
22 |
>> >>> I just look through every so often and make sure everything seems |
23 |
>> >>> to meet those sorts of requirements. When I find a library or |
24 |
>> >>> something else then: |
25 |
>> >>> |
26 |
>> >>> 1) I make sure I'm clean with emerge -DuN @world AND emerge -p |
27 |
>> >>> --depclean 2) I'll delete the questionable item |
28 |
>> >>> 3) I'll see what happens with the two commands in #1 |
29 |
>> >>> |
30 |
>> >>> To me it's pretty straight forward, but I'm also not bothered at |
31 |
>> >>> all by the idea that emerge package and emerge -u package do the |
32 |
>> >>> same thing. A machine that doesn't have a package, when updated, |
33 |
>> >>> should have the package and it should (IMO) be in world, but |
34 |
>> >>> that's just me. |
35 |
>> >> |
36 |
>> >> |
37 |
>> >> Fine for your home PC, doesn't cut it on servers. I have the |
38 |
>> >> following in one of my world files: |
39 |
>> >> |
40 |
>> >> dev-php/PEAR-Mail |
41 |
>> >> dev-php/PEAR-Mail_Mime |
42 |
>> >> dev-php/PEAR-PEAR |
43 |
>> >> dev-php/PEAR-Structures_Graph |
44 |
>> >> |
45 |
>> >> which of those do I want? At least one of them was installed to |
46 |
>> >> support a customer's custom PHP application. Maybe all of them |
47 |
>> >> were and they all belong in world. No one knows, this server is |
48 |
>> >> older than the current --update behavior. |
49 |
>> >> |
50 |
>> >> So which ones can I remove? |
51 |
>> >> |
52 |
>> >> Solutions involving time travel and/or losing customers will be |
53 |
>> >> disqualified. |
54 |
>> > |
55 |
>> > Make a backup copy of your world file. |
56 |
>> > |
57 |
>> > 1a. Remove those four lines. |
58 |
>> > 2a. emerge -p --depclean |
59 |
>> > 3a. Did any of those show up in the to-be-removed set? Add them |
60 |
>> > back. |
61 |
>> > |
62 |
>> > Alternately: |
63 |
>> > 1b. emerge -pev --tree --with-bdeps=y @world |
64 |
>> > 2b Find those packages in the output. The tree form of the display |
65 |
>> > will help you see if anything is depending on them. |
66 |
>> > 3b. If anything is depending on them, you should be able to safely |
67 |
>> > remove them from your world file. I'd follow up with the 1a, 2a, 3a |
68 |
>> > solution to be sure. |
69 |
>> |
70 |
>> It just occurred to me...in the future, you might be able to build |
71 |
>> ebuilds for managing customer requests, to ensure that dependencies on |
72 |
>> particular packages with USE flags and version requirements are met. |
73 |
>> |
74 |
>> I haven't built ebuilds myself yet, but it's on my TODO list. |
75 |
>> |
76 |
> |
77 |
> It's quite easy actually, doubly so if the package follows some sane |
78 |
> rational build process (like eg configure && make && make install). In |
79 |
> that case the ebuild is very small as the portage framework does all |
80 |
> the heavy lifting automagically. |
81 |
> |
82 |
> I'd move that TODO item higher up on the priority list if I were you, |
83 |
> you'll be glad you did :-) |
84 |
|
85 |
Oh, I know. There's a bunch of things I want to add or fix. Even if |
86 |
that means taking some degree of ownership of them. |
87 |
|
88 |
-- |
89 |
:wq |