Alan McKinnon <alan.mckinnon <at> gmail.com> writes:
> > I'll add --oneshot to the EMERGE_DEFAULT_OPTS= in make.conf. > >> I sometimes wonder why that isn't the default way. I guess because it > >> would confuse folks for a bit and because it has always been that way. > > One thing I see, is now you have a system that is full of pkg that do > > not update normally. I guess I'm say if you install pakages with --oneshot, > > they are not automatically updated, or are they? (discussion). > > 'emerge -uDNv world' is the most common form of update, probably, used > > by gentoo users. So how to best ferret out those oneshot packages for > > update; and that's if they should be updated.... semantics on that? > I think you two have it backwards. mostly true for routine users. I myself find myself testing codes and inter operability between codes and stuff I write, more that just installing from the portage tree. I guess you could say I'm moving from user to hacker status (with extreme prejudice). I do not alway remember (-1); particularly when manually cleansing problems like the recent ncurses episode. I like Dale's approach. I just need a tool option or simple script that tells me what is installed and not in @system or @world. Surely this code/option exist and I have just missed it in the literature? > The intended workflow is that if you emerge something, you know what it > is, you don't have to make further decisions about it and you want it > in world. users yes, hackers no. For a long time, I just used gentoo. Now I'm coding (specifcations --> architecture --> then code) and hacking (modifying other codes) quite a lot. I have a robust world file that migrates from workstation to workstation and only update it, replace pkgs, or add a select few niftyones, like trace-cmd and heaptrack. So I'm not suggesting this for normal, new gentoo users. <at> world, by definition, is the list of packages you want. That plus <at> system plus all deps constitutes the set of what should be on the system, anything you have not in that set is subject to depcleaning true. If you are not sure about some package, by all means emerge it with -1. Check it out, verify it, make sure it does what you want then get it in world with emerge -n. Why would you want to have stuff around for extended periods that is not in world? Again, user focused, mostly true. If you have a package that you no longer want (as you know what is in your world right), unmerge it with -C It's not that simple. I'm spending a large amount of my gentoo-admin time installing--testing--marinating--modifying--testing--removal. Dale's simple suggesting is brilliant for my needs. (thx Dale). Don't make life difficult for yourself. It's MUCH easier to know what's in world than to try and remember what should be and isn't. Users (YES) hackers(??? no in my case). Sorry bro, I'm running with Dale in this one. Now, I still need a --oneshot parser solution for vdb (/var/db/pkg/)? 1] Glep-64 preliminary code? 2] a DAG? 3] Neil's mod to CheckInstall? 4] a 'man page option' would be keenest; that I have missed? 5] a script? 6] or a profile? [10] default/linux/amd64/13.0/developer I've been looking for some details on the developer profile; a list of additional packages only or some other keen settings and other goodies ? James
