It's weird that after 222 that they're going strictly to unstable code branches and nightly build monikers.
Trimming down a project is nice and all, and using autogen.sh is fine, but when you halt stable versioned releases, that gets a bit absurd. Tracking bugs on dated git pulls becomes flat out impossible. I've been there, done that, and learned my lesson. Some of these changes of recent to the entire systemd development model just make me wonder what the Hell is going on. I can understand forking of gudev, going to autogen.sh to avoid mismatches with autotools versions and libtool, but stopping stable releases... that's outright odd. -----Original Message----- From: "Armin K." <[email protected]> Sent: 7/11/2015 2:06 AM To: "LFS Developers Mailinglist" <[email protected]> Subject: Re: [lfs-dev] About new systemd release management On 11.07.2015 06:45, James Powell wrote: > I find this of little excuse to not have autotools ready tarballs from the > developer. I too use githib, but you can branch stable code, pull the > sources, and get them package ready in versioned releases. I'm wondering if > this is just laziness or carelessness? > http://lists.freedesktop.org/archives/systemd-devel/2015-June/033214.html Find out for yourself. Unfortunately, Lennart asked if anyone depended on previous setup and I wasn't subscribed at the time to raise my concerns. By the time I found out, it was already late. -- Note: My last name is not Krejzi.
-- http://lists.linuxfromscratch.org/listinfo/lfs-dev FAQ: http://www.linuxfromscratch.org/faq/ Unsubscribe: See the above information page
