2008/6/10 Ira Abramov <[EMAIL PROTECTED]>: > Quoting Amos Shapira, from the post of Sat, 07 Jun: >> >> But can you mark a package as "nothing depends on it, but I want it >> >> around" (lower-case "m" in aptitude) vs. "keep it around as long as >> >> something needs it, but remove it when it's no longer needed by >> >> anything else" (upper-case "M" in aptitude)? >> > >> > I don't know. I never looked for that feature (nor did I know it in >> > aptitude) >> > >> > so I go "aptitude -m liblala" to mark it you say? I tried aptitude >> > --help and it's not mentioned. >> >> It's "markauto" (capital "M" in the interactive interface) and >> "unmarkauto" (lower case "m" in the interactive interdface). Just >> found this from "aptitude --help". > > ahh... but here I thought we were comparing the CLIs of aptitude and > apt-get.
CLI, TUI, ... as long as there is a way to get this kind of functionality working. TUI, as I stated in the quote below, is very useful to allow just hitting "M" and get an instant feedback on what's involved. > >> So I can't give more plausible explanations. 30 seconds sounds closer >> to my experience. > > Anyone knows what this slow "Writing extendad state" stage is? > > and I agree about it being unecessarily verbose: > > uma:~# time aptitude markauto bash > Reading package lists... Done > Building dependency tree... Done > Reading extended state information > Initializing package states... Done > Reading task descriptions... Done > Building tag database... Done > No packages will be installed, upgraded, or removed. > 0 packages upgraded, 0 newly installed, 0 to remove and 0 not upgraded. > Need to get 0B of archives. After unpacking 0B will be used. >>> Writing extended state information... Done<< (that's the slow bit!) So you get this in command line too? How about "strace"? >> then not confirm this but can get long and tadeious. I also learned >> about one of the yum-utils programs which can do something similar but >> not being interactive means it's a lot of typing to go through >> everything. > > well, that's just one more reason I go for CentOS only if my client > absolutely insists, and RHEL if they insist AND bribe me. package > management is so underrated in the non-dpkg world :-( I'm with you on that. BUT that said - we were virtually forced to use CentOS for the hosted servers and I prefer to "break my teeth" on one distro than: 1. Have to learn it anyway for some servers but still maintain scripts/codebase for multiple distros. 2. Have to teach my employees and colleagues about the difference between distros 3. Have to justify to my superiors sticking to yet another distro besides the one we have to use on servers. My own desktop is nobody's business so I can use whatever I want. > > (and SuSE is the worst!) > >> > it's your funural. Ubuntu has proven to be nothing but headache to me so >> > far. >> >> In what way was it a headache? > > weird defaults for workplace lans (no ssh server?!), undocumented It's a bit weird but remember it's probably that way because it's geared towards home users. What about the server edition? Does it miss openssh-server too? Doesn't Ubuntu have some way to customize the installation process (I think I saw references to such a thing)? > NetworkManager behavior (if /etc/network/interfaces is empty and google > is no help - how do I set up the NICs?), not working out of the box in > VMware... and that weird new init procedure that I haven't started > touching yet. At the time I googled around (a few months back) I could > not find a transitional tutorial for all the new gadgetry. If forced, > I'll learn it when it hits Debian and CentOS. I hope documentation is > better these days. Ira - you've been a long time in this field and I expect you should have the experience to see, in retrospect, that many things which looked "weird" and "overblown" and "who needs this?" and "the old way works, why break it?" (gnome vs. KDE vs. Xaw, grub vs. lilo vs. syslinux, cups vs. lp vs. lpr, LVS vs. partitions, GUI web browsers vs. command line and TUI ftp clients, JavaScript, etc) became standard and we got used to them and learned to appreciate their added value. I'm probably just as familiar with the new init process as you are (I just overheard they plan to use something instead of the traditional init) but I guess that it'll either become usable and stick or otherwise will drop off the face of the earth. Cheers, --Amos ================================================================= To unsubscribe, send mail to [EMAIL PROTECTED] with the word "unsubscribe" in the message body, e.g., run the command echo unsubscribe | mail [EMAIL PROTECTED]
