On Sun, Jul 04, 2004 at 04:15:37PM +0800, Andy Sy wrote: > When I started out with Linux back in the 1.x.x kernel days, I tried out > Slackware (3.x iirc) and RedHat (3.x/4.x), . The minute I tried to mix > and match packages I compiled myself into my RH system, I gave up on Redhat > and its infernal RPM system. > > Interestingly enough, ever since then, I never found myself missing/needing > automated dependencies checking... the way Slackware lays out its packages, > it's quite easy to manually figure out which components depend on which. > I have just learned to avoid getting anal about disk space and generally > install > packages by set (no need to remove every small bit of fat). So, for > instance, > if I need X, I generally install all X packages (probably just over a dozen > or > so) that are obviously nonoptional only excluding, for example, non-English > fonts. >
That's nice to hear. Makes me all warm and fuzzy and itching to try out Slackware. Is there by some chance any redistributors of it in Manila? Magpapakuha ako sa pinsan ko kung mayruon... > Have never found myself needing slapt-get, swaret or 3rd party tools like > them > for Slackware package management and I have installed a lot of outside > (non-Slackware) packages from source. (Actually this could be precisely the > reason why a tool like swaret, slapt-get might actually make things more > complicated). I think that if one doesn't have a clear view of which > packages > depend on which, then that counts as 'a little knowledge' which as everyone > knows is a dangerous thing. :-) > True. The worst knowledge is little knowledge, but it is also the most creative. Of course you wouldn't want that in a mission-critical environment, but for those who love breaking boxes to pieces every now and then to get a clue would get burned pretty often. And yes, mixing BFS (build from source) with binary package systems are just an invite for more trouble :D > The standard Slackware pkgtools functionality (plus being clueful enough > to check inside /var/log/packages) essentially gives you Windoze's > Add/Remove > functionality and is even more reliable in that it doesn't sneakily leave > files around when you uninstall. > Yeah. In Debian that's /var/lib/dpkg/*. At least with these package and BFS systems you would know which files get left over after a remove (even a purge)--In windows, for some software (mostly dl'd from the Net , mostly not even by the user ;) you can't even remove them at all w/o fusking a dll or two... Cheers, Zakame -- |=-------------ZAK B. ELEP (Registered Linux User #327585)-------------=| || Web: http://zakame.spunge.org GPG ID: 0xFA53851D || || http://zakame.homelinux.org ICQ UIN: 33236644 || || Location: Daet, Camarines Norte Running Linux 2.6 || |=----------1486 7957 454D E529 E4F1 F75E 5787 B1FD FA53 851D----------=| Debian - When you've got better things to do than to fix a borken system -- Philippine Linux Users' Group (PLUG) Mailing List [EMAIL PROTECTED] (#PLUG @ irc.free.net.ph) Official Website: http://plug.linux.org.ph Searchable Archives: http://marc.free.net.ph . To leave, go to http://lists.q-linux.com/mailman/listinfo/plug . Are you a Linux newbie? To join the newbie list, go to http://lists.q-linux.com/mailman/listinfo/ph-linux-newbie
