On 06/29/2014 09:55 PM, Armin K. wrote: > Hello all, > > As you could see, few moments ago I've commited a "systemd2" branch, > which contains a prototype of how I would try to create and maintain > BLFS systemd book from single (fsvo single) xml source hierarchy. > > So how would I achieve that? > > Since there are far more packages that don't require any modifications > for either systemd or systemv, it would be a bit overkill to maintain a > separate branch, especially since it's impossible to keep up with Fernando. > > I know this has been rejected in the past, but here I go again. Chris > gave me an idea of having two different "chapter" files (the ones that > contain all xincludes from a chapter) and let the "make" process decide > which one should be used. > > So the idea would be to have: > > postlfs/security/security.xml.systemv > postlfs/security/security.xml.systemd > > The first one would be the same as postlfs/security/security.xml > currently is, just renamed. > > Packages that require modifications for systemd would be renamed to do > that, ie > > postlfs/security/polkit.xml would be for systemv setup > postlfs/security/polkit-systemd.xml would be for systemd setup > > The second one would be referenced in > postlfs/security/security.xml.systemd mentioned above. > > This would require a small change to BLFS top level Makefile as well as > renaming the chapter files in the current book. I have commited the > "systemd2" branch for prototyping the chapter "Security". > > Only thing that would change for editors is to make sure they use > chapter.xml.systemv or chapter.xml.systemd instead of chapter.xml for > inclusion of new packages. > > Comments? >
It has been a week since I sent this out and I haven't got a single clear "yes" or "no" from any of the current developers. Should I give up hopes on this? Thanks and sorry for the noise. -- Note: My last name is not Krejzi. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
