1 |
Alan McKinnon <alan.mckinnon <at> gmail.com> writes: |
2 |
|
3 |
|
4 |
|
5 |
> > I'll add --oneshot to the EMERGE_DEFAULT_OPTS= in make.conf. |
6 |
|
7 |
> >> I sometimes wonder why that isn't the default way. I guess because it |
8 |
> >> would confuse folks for a bit and because it has always been that way. |
9 |
|
10 |
> > One thing I see, is now you have a system that is full of pkg that do |
11 |
> > not update normally. I guess I'm say if you install pakages with --oneshot, |
12 |
> > they are not automatically updated, or are they? (discussion). |
13 |
|
14 |
> > 'emerge -uDNv world' is the most common form of update, probably, used |
15 |
> > by gentoo users. So how to best ferret out those oneshot packages for |
16 |
> > update; and that's if they should be updated.... semantics on that? |
17 |
|
18 |
> I think you two have it backwards. |
19 |
|
20 |
mostly true for routine users. I myself find myself testing codes |
21 |
and inter operability between codes and stuff I write, more that |
22 |
just installing from the portage tree. I guess you could say I'm moving |
23 |
from user to hacker status (with extreme prejudice). I do not alway |
24 |
remember (-1); particularly when manually cleansing problems like the recent |
25 |
ncurses episode. I like Dale's approach. I just need a tool option or simple |
26 |
script that tells me what is installed and not in @system or @world. |
27 |
Surely this code/option exist and I have just missed it in the literature? |
28 |
|
29 |
|
30 |
> The intended workflow is that if you emerge something, you know what it |
31 |
> is, you don't have to make further decisions about it and you want it |
32 |
> in world. |
33 |
|
34 |
users yes, hackers no. For a long time, I just used gentoo. |
35 |
Now I'm coding (specifcations --> architecture --> then code) |
36 |
and hacking (modifying other codes) quite a lot. I have a robust |
37 |
world file that migrates from workstation to workstation and only |
38 |
update it, replace pkgs, or add a select few niftyones, like |
39 |
trace-cmd and heaptrack. |
40 |
|
41 |
So I'm not suggesting this for normal, new gentoo users. |
42 |
|
43 |
|
44 |
<at> world, by definition, is the list of packages you want. That plus |
45 |
<at> system plus all deps constitutes the set of what should be on the |
46 |
system, anything you have not in that set is subject to depcleaning |
47 |
|
48 |
true. |
49 |
|
50 |
If you are not sure about some package, by all means emerge it with -1. |
51 |
Check it out, verify it, make sure it does what you want then get it in |
52 |
world with emerge -n. Why would you want to have stuff around for |
53 |
extended periods that is not in world? |
54 |
|
55 |
Again, user focused, mostly true. |
56 |
|
57 |
If you have a package that you no longer want (as you know what is in |
58 |
your world right), unmerge it with -C |
59 |
|
60 |
It's not that simple. I'm spending a large amount of my gentoo-admin |
61 |
time installing--testing--marinating--modifying--testing--removal. |
62 |
Dale's simple suggesting is brilliant for my needs. (thx Dale). |
63 |
|
64 |
Don't make life difficult for yourself. It's MUCH easier to know what's |
65 |
in world than to try and remember what should be and isn't. |
66 |
|
67 |
Users (YES) hackers(??? no in my case). |
68 |
|
69 |
Sorry bro, I'm running with Dale in this one. |
70 |
|
71 |
Now, I still need a --oneshot parser solution for vdb (/var/db/pkg/)? |
72 |
1] Glep-64 preliminary code? |
73 |
2] a DAG? |
74 |
3] Neil's mod to CheckInstall? |
75 |
4] a 'man page option' would be keenest; that I have missed? |
76 |
5] a script? |
77 |
6] or a profile? [10] default/linux/amd64/13.0/developer |
78 |
|
79 |
I've been looking for some details on the developer profile; |
80 |
a list of additional packages only or some other keen settings |
81 |
and other goodies ? |
82 |
|
83 |
|
84 |
|
85 |
James |