On Fri, May 15, 2015 at 11:32:59AM -0700, Paul Rogers wrote: > The book presents a top layer in alphabetical order, with dependencies > underneath. So our job is made much more tedious and difficult, hand > (re)making the dependency trees to see which are lowest-level to be made > first. May I suggest that if the book order were from lowest level > first, installation order, it would be much easier for us, and eliminate > an error-prone process everybody has to go through separately. >
Many of the dependent modules are external - some are not required for a build of the module which uses them (e.g. in modules I build for biber, a lot of extra modules are needed at each stage to get the testsuites all working - and after my first experience with biber-1.9 I now run the tests in the modules). > Yes, I know the counter argument is somebody might not have to or want > to install all of them. How would they know that a-priori? I come to > this section with the assumption that if it's in the book that alone is > sufficient reason to install everything there--something or other I may > not discover until later will want me to have installed something here. > I might as well do it now along with everything else. I suggest that you start by identifying which modules you want to install (i.e. treat them like everything else in the book - some final package has required and optional dependencies. And please note that in some parts of the book there are mutually-exclusive packages (the canonical example is mail servers - the presence of a sendmail program is often checked for, but in my case it comes from postfix). > > Failing that argument being persuasive, does anybody here HAVE a list of > the modules in the proper installation dependency order they could > contribute to me? I'd be ever so grateful. TIA I build the proverbial shed-load of perl modules, but for different things. A few of them get used for some audio-video stuff (e.g. get_iplayer, which will be of no use to people accessing the BBC from outside GB - unless they work around the restrictions, and for what is now on the BBC it probably isn't worth it unless you are an expat Briton), one or two get built on server (test) builds, but the vast majority are for biber. For the modules I build on the desktop, I can probably provide some notes - but they are for my use cases. I'll reply to this in a while when I'm back at a desktop system (the netbook is too restrictive to manage this comfortable). ĸen -- Nanny Ogg usually went to bed early. After all, she was an old lady. Sometimes she went to bed as early as 6 a.m. -- http://lists.linuxfromscratch.org/listinfo/blfs-support FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
