I got pulled off on a project for work and will have to read all the below in detail later, but in general it does not matter if a source tree contains auto-generated files or broken out separately. I just got confused by the docs on linuxcnc.org and did not see any tagged sources out yet. So any of the sources (like http://linuxcnc.org/dists/jessie/2.7-uspace/source/, or https://github.com/jepler/linuxcnc-mirror/releases) will work fine, I just need to know which are considered the canonical ones for the releases. At the moment we are copying these off onto sourceforge so we know we will have them over the long haul.
Also as a side note, I can set things up to grab versions supplied by git/mecurial/etc., but that is considered bad form because the repositories have a habit of changing, and unless the versions are tagged the behaviour changes at compile time. We call these "live" ebuilds in the Gentoo community... More later, EBo -- On Sep 6 2015 12:26 PM, Jeff Epler wrote: > As always, I'm not familiar with Gentoo packaging. Do they have a > way > to specify that the upstream source comes from git? Or does the > source > tarball remain the canonical form for upstream source? > > Our Debian packaging always generates source tarballs. These > tarballs > are what is in our git at the corresponding tag, plus some > autogenerated > files in the debian/ directory. These autogenerated files are a > little > different for each OS version and rtai vs uspace realtime. If you > know > a little about the layout of Debian archives, you can always find > them. > For instance, the exact tarball that we build for Debian jessie and > uspace realtime is in > http://linuxcnc.org/dists/jessie/2.7-uspace/source/ > and the 2.7.0 tarball is > > http://linuxcnc.org/dists/jessie/2.7-uspace/source/linuxcnc_2.7.0.tar.xz > (everywhere under dists/ will provide directory listings) > > You can also create tarball yourself. For 2.7.0, Seb has provided a > signed tag v2.7.0; you can use gpg to verify that this is the exact > version that Seb tagged. You can get this tarball from our > unofficial > github mirror's "releases" page > https://github.com/jepler/linuxcnc-mirror/releases > or using the git command "git archive", which can work on a local or > a > remote git repository. (either git.linuxcnc.org or github will work > for > that) > > All that virtual ink having been spilled, is there more we need to do > for non-debian distros as far as promoting or making obvious these > ways > to obtain a tarball? What information would an ideal release > announcement hold? Does it matter that the tarballs we have on > www.linuxcnc.org contain a small amount of autogenerated files that > is > not in our git? > > Jeff > > > ------------------------------------------------------------------------------ > _______________________________________________ > Emc-developers mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/emc-developers ------------------------------------------------------------------------------ _______________________________________________ Emc-developers mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/emc-developers
