Re: Installing HAL
Scott Castaline wrote: I wanted to install automount, but the book recommended using HAL. Going through the text on HAL it leads you to what appears to be circular required dependencies. On HAL you need both D-BUS GLib Bindings-0.74 and XML::Parser-2.34. First going down the D-Bus path I need dbus-glib-0.74, which in turn needs D-BUS-1.0.2, GLib-2.12.12, and epat-2.0.1. First going down the D-Bus path I need expat-2.0.1, or pkg-config-0.22, and libxml2-2.6.31. So I originally said okay go with expat-2.0.1, which does end that path. Okay so I should be able to install expat-2.0.1, go back and install dbus-1.0.2. Now onto the 2nd prerequisite dbus-glib-0.74, which is glib-2.12.12, which requires pkg-config-0.22 an alternate requirement for dbus-1.0.2. Fortunately there are no further requirements on that path so installing pkg-config-0.22 I should be able to install glib-2.12.12, which will once again bring me back to dbus-glib-0.74.tar.gz and since the 3rd prerequisite is expat-2.0.1 and that was installed following the first path of dbus-1.0.2 I should be able to now install dbus-glib-0.74. Now I should be able to continue down the 2nd prerequisite for installing HAL, XML::Parser-2.34, which makes mention of being installed with the standard Perl module build/install, as well as again expat-2.0.1 Now for the question(s): 1. What order should I go in building and installing? My thinking was install in the following order: expat-2.0.1 -- dbus-1.0.2 -- pkg-config-0.22 -- glib-2.12.12 -- dbus-glib-0.74. 2. During the lfs build wasn't the Perl Module installed and did that include the module extension XML-Parser-2.34? 3. HAL-0.5.9.1 lists an optional package of libxml2-2.6.31, which lists as optional libxslt-1.1.22 and Python-2.5.2. (Python I've already installed), libxslt-1.1.22 lists libxml2-2.6.31 as required. So should I install that first then install libxml and back to HAL? I just noticed that an optional package for dbus-1.0.2 is X Window System and Doxygen which the latter was also listed also as an option to another pkge. I'm planning on eventually installing X but was thinking later. Should I do it now and then come back to all of this? Or can I just rebuild/reinstall these pkgs individually without going through all of them again? Sorry to hit with so much at one time, but to me it looks like I need to know all this now b4 moving on. Also I have 4.8 GB left on my drive, will that be enough or should I now plan on making more room? -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Installing HAL
Scott Castaline wrote: [snip total confusion :-)] I'll try and be helpful without sounding condescending. First. You need to get a handle on what packages do, and why they are dependencies of one-another. For example, Doxygen is only used to create API documentation. Chances are, you don't even need it. Without knowing *why* a package is a dependency, you'll be asking questions until the cows come home. Next. Most circular dependencies in BLFS are annotated one way or another. There are actually very few. Read the dependencies *carefully*. Examine what each one does, and how/why it could benefit your installation. If you don't understand what a package does by reading the stuff in BLFS or the stuff on the home page of the package, chances are you don't need it. Next. I build X right off the bat. Expat, then FreeType and Fontconfig, then X (hopefully, I'm not leaving something out). The dependencies for X are very straightforward. As far as D-Bus/Hal, it really isn't that hard. If I remember correctly, there may be a circular dependency, but only for a package that you may not need. I can't recall, and don't have time to go through the BLFS book right now. Use your good judgment, but above all know *why* you are installing each and every package. Simply going through the book blindly installing packages won't give you the knowledge you could get by understanding *what* each package does. Finally, know that you can always go back and install a package again if you later discover you left off a dependency you wish you had installed. It is a learning process. If that learning process is not *fun* to you, you may consider simply going back to a distro. Also I have 4.8 GB left on my drive, will that be enough or should I now plan on making more room? I know it would not be near enough for me. But I keep all source files, and all logs (I don't keep source trees). I usually end up using around 10MB of space for a full BLFS build. But I'm a BLFS dev and I try to install most dependencies simply so I can document and check them out. I don't necessarily use all of them. Keep in mind that if you're going to do any video/audio processing work, or creating DVD's, you'll need much, much more space. HTH. -- Randy -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Installing HAL
On Tue, Oct 07, 2008 at 04:31:20PM -0400, Scott Castaline wrote: Scott Castaline wrote: I just noticed that an optional package for dbus-1.0.2 is X Window System and Doxygen which the latter was also listed also as an option to another pkge. I'm planning on eventually installing X but was thinking later. Should I do it now and then come back to all of this? Or can I just rebuild/reinstall these pkgs individually without going through all of them again? Sorry to hit with so much at one time, but to me it looks like I need to know all this now b4 moving on. Also I have 4.8 GB left on my drive, will that be enough or should I now plan on making more room? I have an abhorrence of hal, and will go out of my way to avoid it (but, I equally avoid automount). However, to answer your last question first, yes, install X first. Dbus seems to be required by modern desktop systems, it may even be useful, but without X you won't have a desktop. Since the book is mostly still at the 6.3 stage, here is part of my build order for those versions, somewhat modified to match what I'm now doing (I used to defer dbus until I built the gnome apps I needed, here it is moved earlier ]: ed, expat, libpng, Python, libxml2, libxslt, gperf, freetype, fontconfig, XML-Parser, intltool, pkgconfig xorg. Until you know what parts you *don't* want, follow the wget files (for some of these parts, the order in which you build them is important - the order in the wget files works) protos, utilities, libraries, libdrm, Mesa (people using nvidia hardware can probably drop this, bitmaps, apps, core fonts [ at a minimum, encodings, font-util, font-adobe in 100dpi or 75dpi to match your screen, font-alias, font-cursor, font-misc-misc ], xorg-server, drivers (input and video), TTFs of your choice, a basic windowmanager (I've given up on twm, which the book has among the apps, I think - fluxbox works adequately enough for me until I've built the toolkits and can build e.g. icewm (use 1.3 if you are doing that) or whatever else you prefer. You'll also need some sort of terminal to do anything in X at this point, the book has xterm (needs luit), or rxvt-unicode. If you intend to use a 'legacy' desktop (twm, possibly even fluxbox) you may wish to install more of the 'core' fonts. Most people will want to use TTFs - if you eventually use gnome applications you probably want many of the TTFs in the book (particularly dejavu which contains whitespace variants that will otherwise be rendered as boxes). After that, you have an embryo desktop and can build a toolkit and the other necessities: jpeglib, [ libtiff - recommended if you will be using gnome ], [ giflib ], lcms, [ libmng (works in kde3, but firefox disdains it as not invented here) ], iso-codes, dbus / bootscript, icon-naming, startup-notification, cairo, glib2, dbus-glib, [ desktop-file-utils ], [ popt ], pango, atk, gtk2, [ QT ]. That's just a starting point, but it is hopefully enough to give you some idea, and to then build gnome or kde if you wish to. If you intend to use any legacy gtk1 applications, you could build glib1 and then gtk1 near the beginning of that part - but, I assume you have taste ;) Your first task is really to sit down with the book, work out what you know you want to try, and then draw up a dependency diagram. ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Installing HAL
On Tue, Oct 07, 2008 at 03:58:02PM -0500, Randy McMurchy wrote: Scott Castaline wrote: Also I have 4.8 GB left on my drive, will that be enough or should I now plan on making more room? I know it would not be near enough for me. But I keep all source files, and all logs (I don't keep source trees). I usually end up using around 10MB of space for a full BLFS build. But I'm a BLFS dev and I try to install most dependencies simply so I can document and check them out. I don't necessarily use all of them. Missed that part. Until I started editing some of the BLFS packages, my '/' partitions were about 3 or 4 GB. I keep /home separate (so that I can share it between successive installations), so what matters is how much space you have apart from where you intend to hold data and notes. If that is 3GB, it's definitely enough to build a lot (but, you might have to strip the files - no big deal if you don't intend to run a debugger on them). ĸen -- das eine Mal als Tragödie, das andere Mal als Farce -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
Re: Installing HAL
Randy McMurchy wrote: Scott Castaline wrote: [snip total confusion :-)] I'll try and be helpful without sounding condescending. First. You need to get a handle on what packages do, and why they are dependencies of one-another. For example, Doxygen is only used to create API documentation. Chances are, you don't even need it. I didn't think I did, just thought that it could be useful for other things. Without knowing *why* a package is a dependency, you'll be asking questions until the cows come home. Next. Most circular dependencies in BLFS are annotated one way or another. There are actually very few. Read the dependencies *carefully*. Examine what each one does, and how/why it could benefit your installation. If you don't understand what a package does by reading the stuff in BLFS or the stuff on the home page of the package, chances are you don't need it. Next. I build X right off the bat. Expat, then FreeType and Fontconfig, then X (hopefully, I'm not leaving something out). The dependencies for X are very straightforward. I wasn't sure if that was the way to go. I had first got wget and then the dhcp packages and a couple of other packages. The automount thing actually came from a cdrom thing, just thought that it would be nice to have, but it looks like that it probably would be better to install X first and then possibly come back to that. In regards to the dependencies, I understand where you are coming from, I just wasn't sure which was the best order to go. As far as D-Bus/Hal, it really isn't that hard. If I remember correctly, there may be a circular dependency, but only for a package that you may not need. I can't recall, and don't have time to go through the BLFS book right now. Use your good judgment, but above all know *why* you are installing each and every package. Simply going through the book blindly installing packages won't give you the knowledge you could get by understanding *what* each package does. Finally, know that you can always go back and install a package again if you later discover you left off a dependency you wish you had installed. It is a learning process. If that learning process is not *fun* to you, you may consider simply going back to a distro. Also I have 4.8 GB left on my drive, will that be enough or should I now plan on making more room? I know it would not be near enough for me. But I keep all source files, and all logs (I don't keep source trees). I usually end up using around 10MB of space for a full BLFS build. But I'm a BLFS dev and I try to install most dependencies simply so I can document and check them out. I don't necessarily use all of them. Keep in mind that if you're going to do any video/audio processing work, or creating DVD's, you'll need much, much more space. HTH. -- http://linuxfromscratch.org/mailman/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
