On 06/01/2016 12:56 AM, Bruce Dubbs wrote:
DJ Lucas wrote:
On 05/31/2016 07:53 PM, Bruce Dubbs wrote:
Those there packages are all in LFS too.
:-) So, that does open the door for the next question, however. What is
the path to merge BLFS books? Is everybody comfortable with how the LFS
merge went and how it is working after the fact? IMO, it was a complete
success! I've still got a bit more to do in chapter 7 device naming to
bring it up to par with SysV, being side by side brings those
omissions to
the forefront, but if BLFS is to be done in similar fashion, might
want to
get started on it sooner rather than later in the release cycle.
Well, it was a fair amount of work for me. I am happy with the results
though. I want to wait for a couple of weeks to start things though. I
need to do a full kde update first and plasma 5.6.5 is due June 14. kf5
5.11 on June 6th, kf5 apps also on June 14th.
The advantage of the 2nd book is that we have already gone up the
learning curve. The drawback is that BLFS is 10x the size of LFS.
I suspect most of the changes are for services like mail servers, etc.
However there are numerous packages that are only in systemd. What I
did for LFS was to do a diff for each package to decide if a different
file was needed. After a while we were able to consolidate a lot of
those files.
I suppose I can create a merge branch any time. The only problem is
that updates need to be made in multiple places unless we just stop
updating trunk. That would be a lot like a package freeze before
release and a ton of upstream packages tend to accumulate.
Given the size and scope of BLFS, I had thought it might be smoother to
get trunk ready to handle sysv/systemd without any additional content,
and
continue development as usual. I believe this will actually be less
disruptive WRT jhalfs than it was for LFS since we already do a profiled
build (still have to handle the menu, can it be reused?). Then, gradually
pull in the necessary systemd changes. It'll make the timeframe larger to
be sure, but I think it would be a smoother overall transition.
Probably a
bit more tedious than a long freeze, but we'll get there. Might also give
a bit of breathing room to Jean-Phillipe and the French translation team
if they are tracking BLFS.
I'm not sure what you mean here. Do you just want to fix trunk's
Makefile to support the revision= attributes and stop updating the
systemd branch? That would certainly be easier from my point of view.
Yes, rather than work in a branch and keep three sets of source in sync,
I figure we make the change for Makefile (and for jhalfs if necessary).
Add the entities to add -systemd to title, editorial staff if we even
separate it (I'd rather not for BLFS), etc. Development continues as it
always has for both branches. Doug and I (and anybody else who would
like to assist) can gradually copy systemd specific bits into trunk
(without affecting SysV), and when we all feel it's ready, change the
nightly scripts to use the merged source. Technical changes continue to
occur in the systemd branch as they always have and then merge to trunk
(preferably at the same time). The merging itself is ultimately
editorial work, not usually very technical, so likely to come in large
bursts of activity, much like the reverse has been over the past few months.
OT: Speaking of which, I love the side-bar navigation in the French
translation here:
http://www.fr.linuxfromscratch.org/view/lfs-stable/index.html
Excellent work guys! I have exactly two nit-picks, to my taste. I'd
freeze
the indent after the large icons show up in the TOCs, and left justify if
using the small icons (there are some big gaps with only 4-6 words per
line in full justification). If it is all or nothing, still left. But
even
with those minor points, this is an excellent change! It scales to
everything I've thrown at it.
That's their css3 work. We looked at it some time ago. I liked it, but
there was some resistance from some editors. That may be something to
incorporate after the BLFS merge.
I was just reminded that this came up before 2015/08/07 (I wasn't active
at that time). I vaguely remember looking at some of Ken's screenshots
and
having a "meh" response, so I didn't on list.
http://anduin.linuxfromscratch.org/~bdubbs/lfs-book-test/prologue/foreword.html
There have obviously been some changes since, but I'm kind of liking most
of it after seeing it tonight. The font is nicer on the French page, and
the nav icons are evenly spaced on the French page. Bruce's version
doesn't have the indent or large header that I didn't like, and is left
justified. There is an issue with the header being indented in portrait
mode on Android Chrome when viewing Bruce's render as well. I think this
was pretty close when Bruce and Ken last left off. I'd like to revisit
the
css3 changes. Too much at once I know, but that presentation is really
nice!
We can keep it in mind. Depending on how the BLFS merge goes, we might
want to do it before the next release. The scheduled package freeze for
that is in about 10 weeks (mid August), but the exact day will depend on
what packages are pending from upstream.
I'd suggest taking again the changes from www.fr..., as they are now,
since that seems to have less visual anomalies in my quick view last
night, and then see how we look with Ken's previous checks. Then make
modifications for indentation/justification/font/margins if appropriate.
Not sure how old of a browser should be supported, is there no fallback
method for older browsers that don't support CSS3? But again, what we
have now works fine, so no priority. I was just excited, and rather
animated, when I had seen how well it worked on the FR page -- even
after Google Translate had done it's work. I was actually just trying to
gauge how much additional work was created for the FR team (my French is
basically non-existent). Anyway, it certainly goes a long way to
modernizing the look of the online book.
--DJ
--
http://lists.linuxfromscratch.org/listinfo/blfs-dev
FAQ: http://www.linuxfromscratch.org/blfs/faq.html
Unsubscribe: See the above information page
