On Sun, 2014-11-02 at 21:43 +0100, Armin K. wrote: > > Error verifying signature: Failed > to execute gpg. > Lengthy post ahead, go ahead and grab some popcorn or juice. > > Hi everyone, > > For some time now you may have noticed a new BLFS branch managed by me > named "krejzi". > > That branch was branched off BLFS trunk while adding and improving > instructions from BLFS systemd and improving instructions from trunk > (most of them were cosmetic tweaks as I seem to be a consistency freak). > > It's what I call a fork of the BLFS systemd book maintained by me. While > I do not intend to push back the systemd branch I have received many > complains about stuff from systemd branch not working very well recently. > > As a LFS systemd maintainer I feel like it's my duty to provide a stable > (or at least "just working") instructions for BLFS, but I had no other > way to do so than to start my own branch since users don't really care > about reporting issues on mailing lists or bugzilla and for personal > reasons, I don't want either. > > The branch is now in a usable state - in a state where systemd branch > should've been - minus two packages that I have yet to review and fix up > (and, for the latter, to sync with the main book instructions) - lxdm > and polari. Most if not all of the issues have been addressed (maybe > some got slipped during the merge). > > The book will be published online, but not as an official release (ie, > won't be visible from main website) and will most likely be placed on my > personal web space www.lfs.org/~krejzi rather than having a new book at > www.lfs.org/blfs/view/whatever. > > But, I will link from LFS systemd pages (where needed) to the new book > because of the reasons above and probably will make an official release > snapshot when the time is right so the users of LFS systemd have a > stable (as much as trunk is actually, minus the new packages which > aren't many) and always (or at least 99% of the time) working > instructions for whatever they need and with help of Bruce's currency > scripts it will be easy to manage. > > But enough about ranting and stuff like that, I have some questions. > > What I was unable to think of is a proper name for new book. I went with > systemd-ng (ng = new generation) but I instantly received a complaint so > the branch got renamed after just few hours. The branding in the XML > still remains but I'd like to use some different name if possible and > I'm interested in suggestions on how to name it. > > Also, instead of svn (where it was hosted until yesterday), I moved to > github and will continue to manage my fork using git fom now on. > Repository can be found at https://github.com/elkrejzi/BLFS > > If any of the current editors want to contribute directly, just mail me > your public SSH key in order to gain commit access. > > I have yet to publish a rendered version, but when the time is right, > I'll do so and will properly announce it. This mail is just for the > current developers (and possibly users). > > Any comments, rants, critics are welcome. > > I ain't sorry for the long post, but I am for all the hastle that this > post might create. > > -- > http://lists.linuxfromscratch.org/listinfo/blfs-dev > FAQ: http://www.linuxfromscratch.org/blfs/faq.html > Unsubscribe: See the above information page
Funny how things worked for me with testing it after you got shitty and WALKED away from the branch prior to release without actually bothering to officially say so. Not to mention the fact that you did not bother runtime testing some of your unit files that I changed to make work. Though I believe that you already knew when you wrote this that I would not allow you to get away with your false accusations. I can assure you that I will NOT accept any of your updates in the systemd branch in the future. Christopher. -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
