Re: [systemd-devel] no tar balls at release time
On Tue, Jun 23, 2015 at 01:19:54PM +0200, Kay Sievers wrote: > On Tue, Jun 23, 2015 at 4:02 AM, Dave Reisner wrote: > > On Tue, Jun 23, 2015 at 01:21:36AM +0200, Kay Sievers wrote: > >> We currently considering to stop creating release tar balls. > > > > What's the motivation for this change? > > We focus on git, and git only. We do not want to sign tar balls to > distribute, but rely on signed git tags only. > > Pre-building stuff to put into tar balls creates too many > restrictions. It is just plain wrong to pre-build and ship things like > man pages, which depend on common configure options. > > > I suspect that with this, 'make > > distcheck' will never again be run and it will eventually break > > build configurations which don't align with what the CI tests. > > We synced the "make dist" and "git archive" tar balls as much as > possible now. Even the autotools created one will not contain any > pre-built stuff anymore besides the autofoo itself. > > We might continue to run distcheck in the CI, but we don't know > anything for sure at that point in time, only that tar balls are not > part of the release anymore. To reiterate -- Arch doesn't care about tarballs going away. I'm concerned that 'distcheck' provided some amount of pre-release sanity checking, and I'd prefer that we don't lose that for a project which already lacks a large amount of in-tree test coverage. Everyone involved would benefit from something such as the following: implement the equivalent of the kernels 'make allconfig' and use this for the CI builds, rather than a bare "./configure" (which won't pull in much based on the deps being installed). I realize this can't be 100% of the options since there's conflicting and "legacy" switches (like split-usr). However, you'll at least be giving build system more thorough testing, and decreasing the likelihood that release day is when broken builds are reported on the mailing list. dR ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] no tar balls at release time
On Tue, Jun 23, 2015 at 4:02 AM, Dave Reisner wrote: > On Tue, Jun 23, 2015 at 01:21:36AM +0200, Kay Sievers wrote: >> We currently considering to stop creating release tar balls. > > What's the motivation for this change? We focus on git, and git only. We do not want to sign tar balls to distribute, but rely on signed git tags only. Pre-building stuff to put into tar balls creates too many restrictions. It is just plain wrong to pre-build and ship things like man pages, which depend on common configure options. > I suspect that with this, 'make > distcheck' will never again be run and it will eventually break > build configurations which don't align with what the CI tests. We synced the "make dist" and "git archive" tar balls as much as possible now. Even the autotools created one will not contain any pre-built stuff anymore besides the autofoo itself. We might continue to run distcheck in the CI, but we don't know anything for sure at that point in time, only that tar balls are not part of the release anymore. Kay ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] no tar balls at release time
On Mon, Jun 22, 2015 at 10:21:18PM -0400, Mike Gilbert wrote: > On Mon, Jun 22, 2015 at 7:30 PM, Lennart Poettering > wrote: > > On Tue, 23.06.15 01:21, Kay Sievers (k...@vrfy.org) wrote: > > > >> We currently considering to stop creating release tar balls. > >> > >> For build systems which still require them, they can be created > >> locally from the upstream git repository with: > >> git archive --format=tar --prefix=systemd-$(VERSION)/ $(VERSION) | \ > >> xz > systemd-$(VERSION).tar.xz > >> > >> These tar balls will not include the "500k of shell scripts" added by > >> autotools. These files need to be added to the extracted tarball by > >> running ./autogen.sh. > >> > >> These tar balls will also not include any generated content like > >> fonts, man, html pages. This is intentional. > > > > Which of course means the build tools for all of these need to be > > around on the build machines, as *everything* will be rebuilt from > > scratch now. Specifically you need > > autoconf/automake/python/perl/m4/xsltproc/... on every build machine. > > > > Hence the question to ask is: is anyone downstream relying on the > > pre-built stuff, and has a very good reason why he couldn't just > > install the build tools on his build machine and build things with > > that? > > On Gentoo, most users build from source, so this means additional > dependencies on most users' systems. We would appreciate having the > autotools-generated tarballs, but we can certainly live without them. > > FYI, having to run autoreconf introduces the following dependencies for us: > > app-text/docbook-xml-dtd:4.2 > app-text/docbook-xml-dtd:4.5 > app-text/docbook-xsl-stylesheets > dev-libs/libxslt:0 > >=dev-libs/libgcrypt-1.4.5:0" I don't mind the autotools requirements. But building libgcrypt just for autogen is really annoying when cross-compiling for systems where libgcrypt isn't installed at all. So, if you do this, please add all necessary m4 files to the tarballs or make it optional, the way gtk-doc was handled. Regards, Michael -- Pengutronix e.K. | | Industrial Linux Solutions | http://www.pengutronix.de/ | Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0| Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917- | ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] no tar balls at release time
On 23 June 2015 at 00:21, Kay Sievers wrote: > > We currently considering to stop creating release tar balls. > > For build systems which still require them, they can be created > locally from the upstream git repository with: > git archive --format=tar --prefix=systemd-$(VERSION)/ $(VERSION) | \ > xz > systemd-$(VERSION).tar.xz > Or simply "download" the github generated tarball from tag, which is called "releases" Fine by me. We ended up patching configury for us, hence have to autoreconf the lot anyway. -- Regards, Dimitri. Pura Vida! https://clearlinux.org Open Source Technology Center Intel Corporation (UK) Ltd. - Co. Reg. #1134945 - Pipers Way, Swindon SN3 1RJ. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] no tar balls at release time
Kay Sievers [2015-06-23 1:21 +0200]: > Please test these setups locally if that model will work in your > setups, and what would possibly need to be fixed in the git tree to > make that easier for you. Fine for Debian/Ubuntu. We've always rebuilt the autoconfiscation anyway, and our build system also handles package builds straight from a git checkout (for CI). Martin -- Martin Pitt| http://www.piware.de Ubuntu Developer (www.ubuntu.com) | Debian Developer (www.debian.org) ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] no tar balls at release time
On Mon, Jun 22, 2015 at 10:21 PM, Mike Gilbert wrote: > On Mon, Jun 22, 2015 at 7:30 PM, Lennart Poettering > wrote: >> On Tue, 23.06.15 01:21, Kay Sievers (k...@vrfy.org) wrote: >> >>> We currently considering to stop creating release tar balls. >>> >>> For build systems which still require them, they can be created >>> locally from the upstream git repository with: >>> git archive --format=tar --prefix=systemd-$(VERSION)/ $(VERSION) | \ >>> xz > systemd-$(VERSION).tar.xz >>> >>> These tar balls will not include the "500k of shell scripts" added by >>> autotools. These files need to be added to the extracted tarball by >>> running ./autogen.sh. >>> >>> These tar balls will also not include any generated content like >>> fonts, man, html pages. This is intentional. >> >> Which of course means the build tools for all of these need to be >> around on the build machines, as *everything* will be rebuilt from >> scratch now. Specifically you need >> autoconf/automake/python/perl/m4/xsltproc/... on every build machine. >> >> Hence the question to ask is: is anyone downstream relying on the >> pre-built stuff, and has a very good reason why he couldn't just >> install the build tools on his build machine and build things with >> that? > > On Gentoo, most users build from source, so this means additional > dependencies on most users' systems. We would appreciate having the > autotools-generated tarballs, but we can certainly live without them. > > FYI, having to run autoreconf introduces the following dependencies for us: > > app-text/docbook-xml-dtd:4.2 > app-text/docbook-xml-dtd:4.5 > app-text/docbook-xsl-stylesheets > dev-libs/libxslt:0 > >=dev-libs/libgcrypt-1.4.5:0" Plus autoconf/automake/libtools, etc. ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] no tar balls at release time
On Mon, Jun 22, 2015 at 7:30 PM, Lennart Poettering wrote: > On Tue, 23.06.15 01:21, Kay Sievers (k...@vrfy.org) wrote: > >> We currently considering to stop creating release tar balls. >> >> For build systems which still require them, they can be created >> locally from the upstream git repository with: >> git archive --format=tar --prefix=systemd-$(VERSION)/ $(VERSION) | \ >> xz > systemd-$(VERSION).tar.xz >> >> These tar balls will not include the "500k of shell scripts" added by >> autotools. These files need to be added to the extracted tarball by >> running ./autogen.sh. >> >> These tar balls will also not include any generated content like >> fonts, man, html pages. This is intentional. > > Which of course means the build tools for all of these need to be > around on the build machines, as *everything* will be rebuilt from > scratch now. Specifically you need > autoconf/automake/python/perl/m4/xsltproc/... on every build machine. > > Hence the question to ask is: is anyone downstream relying on the > pre-built stuff, and has a very good reason why he couldn't just > install the build tools on his build machine and build things with > that? On Gentoo, most users build from source, so this means additional dependencies on most users' systems. We would appreciate having the autotools-generated tarballs, but we can certainly live without them. FYI, having to run autoreconf introduces the following dependencies for us: app-text/docbook-xml-dtd:4.2 app-text/docbook-xml-dtd:4.5 app-text/docbook-xsl-stylesheets dev-libs/libxslt:0 >=dev-libs/libgcrypt-1.4.5:0" ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] no tar balls at release time
On Tue, Jun 23, 2015 at 01:21:36AM +0200, Kay Sievers wrote: > We currently considering to stop creating release tar balls. What's the motivation for this change? I suspect that with this, 'make distcheck' will never again be run and it will eventually break build configurations which don't align with what the CI tests. > For build systems which still require them, they can be created > locally from the upstream git repository with: > git archive --format=tar --prefix=systemd-$(VERSION)/ $(VERSION) | \ > xz > systemd-$(VERSION).tar.xz > > These tar balls will not include the "500k of shell scripts" added by > autotools. These files need to be added to the extracted tarball by > running ./autogen.sh. > > These tar balls will also not include any generated content like > fonts, man, html pages. This is intentional. > > Please test these setups locally if that model will work in your > setups, and what would possibly need to be fixed in the git tree to > make that easier for you. Arch switched over to the git repo directly when it was discovered that the v220 tarball wasn't useful. We didn't bother going back to the tarballs with v221, either. Seems fine. dR ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
Re: [systemd-devel] no tar balls at release time
On Tue, 23.06.15 01:21, Kay Sievers (k...@vrfy.org) wrote: > We currently considering to stop creating release tar balls. > > For build systems which still require them, they can be created > locally from the upstream git repository with: > git archive --format=tar --prefix=systemd-$(VERSION)/ $(VERSION) | \ > xz > systemd-$(VERSION).tar.xz > > These tar balls will not include the "500k of shell scripts" added by > autotools. These files need to be added to the extracted tarball by > running ./autogen.sh. > > These tar balls will also not include any generated content like > fonts, man, html pages. This is intentional. Which of course means the build tools for all of these need to be around on the build machines, as *everything* will be rebuilt from scratch now. Specifically you need autoconf/automake/python/perl/m4/xsltproc/... on every build machine. Hence the question to ask is: is anyone downstream relying on the pre-built stuff, and has a very good reason why he couldn't just install the build tools on his build machine and build things with that? Are there any other reasons why the automake tarball would be preferable over the git archive tarball? Lennart ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
[systemd-devel] no tar balls at release time
We currently considering to stop creating release tar balls. For build systems which still require them, they can be created locally from the upstream git repository with: git archive --format=tar --prefix=systemd-$(VERSION)/ $(VERSION) | \ xz > systemd-$(VERSION).tar.xz These tar balls will not include the "500k of shell scripts" added by autotools. These files need to be added to the extracted tarball by running ./autogen.sh. These tar balls will also not include any generated content like fonts, man, html pages. This is intentional. Please test these setups locally if that model will work in your setups, and what would possibly need to be fixed in the git tree to make that easier for you. The Fedora build setup was happy without any adjustments to take the git created tar ball instead of the autotools created one. Thanks, Kay ___ systemd-devel mailing list systemd-devel@lists.freedesktop.org http://lists.freedesktop.org/mailman/listinfo/systemd-devel
