On 06/01/2016 11:49 PM, DJ Lucas wrote:
I'd rather only clean the files we create. Who knows if somebody else uses ~/tmp. I originally used the variables, but that means REV has to be set to get the alternates. We really can't do anything if the user changes the value of those variables. I'm okay with blfs* as that still handles the case of building both books one after the other (first pass isn't skipped). Also, after thinking about it a bit, is there any way that it makes sense to depend on $REV for the bootscripts and systemd-units tarballs? We don't do automated md5sum updates AFAICT, and they haven't been dependencies of the all or blfs targets for several years IIRC.
Okay, I went with that. I don't know how to handle the post-commit hook to regenerate the blfs-systemd-units tarball. I took a look around, but all I had seen was the mailer script. I could create a cron job I suppose, but would rather it be handled where/how the other is. I manually created the tarball and dropped it into the correct directory for the time being.
The other big thing that is missing is the "(Systemd version)" string for the page headers. I'll look at that Friday if somebody else doesn't get to it first, but bootscripts/units should pretty much be good to go as is (I just reused the bootscripts xrefs as had already been done in the systemd branch).
Moving on, I believe that there are a couple of cases where the upstream package ships a unit file so that the bootscripts blob needs revision="sysv", but those (assuming I remember correctly) will be caught over the next few days. Beyond that, just corner cases. There are more than a few pages that can't appear in trunk that need to be brought over. Looks like 25 instances of dependencies on systemd that need to be updated (with revision="systemd" tags) and really, just a few cases of special instructions (networking, PAM, dbus, logging, cron, ntp, etc.). Overall, not nearly as scary as I had expected. I was planning on a month of merges, but that seems terribly exaggerated now. I'm probably oversimplifying, in fact, I'm fairly sure I am, but those are the big items anyway.
--DJ -- http://lists.linuxfromscratch.org/listinfo/blfs-dev FAQ: http://www.linuxfromscratch.org/blfs/faq.html Unsubscribe: See the above information page
