On 07/01/2014 10:35 πμ, akhiezer wrote: >> Date: Sat, 04 Jan 2014 14:06:51 +0200 >> From: Thanos Baloukas <[email protected]> >> To: [email protected] >> Subject: Re: [blfs-support] Destdir installation question >> > . > . >> the --keep-directory-symlink seems to be the suitable option. >> By tar manual: >> >> ???--keep-directory-symlink??? >> This option changes the behavior of tar when it encounters a symlink >> with the same name as the directory that it is about to extract. By >> default, in this case tar would first remove the symlink and then >> proceed extracting the directory. >> >> The ???--keep-directory-symlink??? option disables this behavior and >> instructs tar to follow symlinks to directories when extracting from the >> archive. >> >> It is mainly intended to provide compatibility with the Slackware >> installation scripts. >> > > > - just to perhaps clarify (e.g. anyone reading 'cold'), that's of course > new in the relatively-recent 1.27.x release (I'd 'omitted to remember' that > 1.27.x had been released and e.g. added to lfs-svn): it basically restores > some functionality 'lost' when going from 1.13.x to 1.14.x back at the > Eggert->Poznyakoff maint-transition back in 2001-2004. And of course the > option has much wider usefulness than just for slack-installer. You might > find the also-new '--{keep,skip}-old-files' options to be of use too, at > least within the context of the goals & route that you have. (Tho' of course > as they're new, be sure to have tested fully before putting into any > production (as will happen for slack-installer I'd expect)). >
It seems to me that theese options may be very usefull in some cases, e.g. when you've made an incomplete destdir installation. I'll have them in mind. Till now I've finished Xorg and it started with no problems. I had not difficulties so far, except the burden to update my buildscripts. It's sure that the destdir approach is best suited to people like Thomas who create tarballs for multiple machines or like Bruce and Ken who measure the disk space required etc, for book editing purposes. I don't use any package managment system because I never do package updates. I install a new (B)LFS when I have the time, and I only keep logs of installed files. With destdir I can be sure that these logs are accurate. Before that I was using a timestamp based script and I never new for sure what was installed. I also liked the sense of control that destdir gives me, especially on large packages. I can check what will be installed and where, and if I like it I proceed, or else I can change files' location, or even alter configure options and recompile. If those are worth the additional risk and effort depends on how perfectionist someone is, and I'm a lot. As for the sense of control, I Know that sometimes it can be misleading. Especially after Ken's NB warning. And capitals have their meaning. I'm sure however that even if I end up with a dysfunctional system, through the whole process I will have learned a lot. Thank you all -- Thanos -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
