>I just tried git (Guarded Installation Tool) on a gentoo box. But the >result is not good:
In a broad sense, that's possible with git. It helps the sysadmin, but (s)he has to use it properly--no script is clairvoyant. >But this is not important, maybe I have to configure it... A little bit, depending on how your system is setup. >What I'd like to know is how does it work (i mean internal, not the >user-end commands) ? Vladimir gave you a brief idea. git's task is to find out what changed when you installed the package. (RPM has to be told by the spec file, and git can't make presumptions that it already knows what the system contains.) So it has to look at what WAS there before installation & what's there NOW. (Let the install process monopolize the machine so something you do in a vterm doesn't get confused with what the installation does. And watchout for cron jobs.) Personally, I _like_ the fact that it looks. It gives me some confidence that some oddball make file didn't do something that got missed, and I can use the make file as it was intended, without worrying that tricks, like fakeroot, might not work with this one. >and does it take *always* 5+11 minutes? (I tried twice and it did) It depends on how much **** you have in the directories it has to watch. Did you optimize drive access with hdparm? On a lean, clean system, (and as one builds the early steps of LFS ;-), it isn't so bad. And I, personally, can afford to take the time the one time I do the package install. Call it an "investment". Paul Rogers ([EMAIL PROTECTED]) http://www.xprt.net/~pgrogers/ Rogers' Second Law: "Everything you do communicates." (I do not personally endorse any additions after this line. TANSTAAFL :-) -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
