On 02/07/2010 08:50 PM, Bruce Dubbs wrote: > DJ Lucas wrote: > >> On 02/07/2010 03:41 PM, Bruce Dubbs wrote: >> > >>> Do not use a versioned directory such as /opt/gnome-2.28.2 for the >>> Gnome installation prefix. >>> >>> Is this backwards? I would think it should be "Use a versioned >>> directory..." >>> >>> >>> >> It is correct as is. The intention is to use a symlink to the versioned >> directory, but for the environment variables, we use the link, not the >> actual directory. This so that a new installation is as simple as >> changing the symlink. This leaves a dangling symlink in >> /usr/share/icons/gnome -> nowhere, and a couple of gio modules that will >> be overwritten on the next installation in /usr. >> > Ah, I see now. Perhaps I had a preconceived idea of what you are doing, > but it's the opposite of what I thought. I like your approach. > The idea is specifically to be able to remove the entire installation without breaking anything other than that gnome version. I realize that is not a realistic goal, but it's targeted at the in-place upgrade scenario. One version of Gnome goes, the other takes it's place...as long as it's all ABI compatible (big if, I know). > You say a little bit later: > > "If you've elected to install gnome into /usr, you can skip the rest of > this page." > > I think that needs to be highlighted with more emphasis. Perhaps, > <emphasis role="strong">...</emphasis> is all that it needs. > > I would also change "can" to "should", or maybe even "must". > Yes, it should be explicit, the instructions do not apply if doing a /usr build. Thanks. > Another issue. You assume that /etc/profile sources all the files in > /etc/profile.d. That's not the LFS default. I suggest mentioning that > the methodology in the section "The Bash Shell Startup Files" is needed. > Oh, actually I had assumed that was the expected environment, if you differ, it's your problem. At very least, I think setup of a profile.d directory, and sourcing of the files should be handled by LFS. If you don't follow that very minimum, both gvfs and polkit will fail to work correctly as distributed (both are bash completion scripts) and I'd imagine we'll see other packages in the future as well. I myself have been a stickler for the single /etc/profile until recently (this being the motivation), but I knew I was on my own having only set that up once before to put together the file for JDK.
I'd also like to shoehorn in the LSB bootscripts at some point, at least a minimal set because some packages will use that setup by default as well (CUPS comes to mind immediately though the runlevels would need to be modified). Dan Nicholson's initd-tools package, along with the /lib/lsb/init-functions script (which would have to be minimally modified if separated from the contrib package) and the LSB headers from those files would fill that gap just fine for now, but the ultimate goal is to go all LSB style scripts (the package I put together currently has a problem that I should have fixed a long time ago--drop the "not distro dependent" goal and it would have been). -- DJ Lucas -- This message has been scanned for viruses and dangerous content, and is believed to be clean. -- http://linuxfromscratch.org/mailman/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
