I believe you are correct, Rainer. As far as I know Github 'Releases' are just tags. Github takes tags and in the release section uses tags to define a 'release' which is then compressed for easy download as a single file.
It's not a bad way to implementing a release file. Even for your own use. You could take a list of commit ids that are directly related to the release tarfiles, create tags for those IDs and then you would have a fast way of downloading a tarfile of the source code. Of course that's assuming your release tarfile is just a snapshot of the repo which, as you said, it is not. At the end of the day I think it's a nice way of having a quick and easy download ability for grabbing an exact snapshot of a specific version's repo at a commit ID. But it's not a replacement for the release tarfile you use since, as you pointed out, you do a make dist[check] prior to packaging. -- James -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Rainer Gerhards Sent: Thursday, January 23, 2014 5:59 AM To: rsyslog-users Subject: Re: [rsyslog] rsyslog 7.4.9 (v7-stable) released On Thu, Jan 23, 2014 at 3:13 AM, Igor Sverkos <[email protected]>wrote: > Hi, > > please, could you create a release on GitHub (create a tag) for liblogging? > This would really help packaging an updated rsyslog package (bundling > with a new library from a private mail in an unknown state is not an option). > > Thanks. > Is a "github release" really something we want to have? As far as I have now read (I am still a novice at github) a release seems to be a tarball based on the content of the repo. A proper release, however, needs to be built with "make dist[check]" otherwise folks cannot simply run ./configure. Or does github do the "make dist" (and if so, how does this work for non-autoconf projects)? If a github release is a proper release, I'm happy to add it. If not, I think it will cause confusion. Comments, anyone? Regarding the mailed tarball: that was just a convenience because I did not mange to get the official one up on the server in time. I admit I was too focused on getting the packages done that I forgot to do this before the rsyslog release. That will change today. Rainer _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT. _______________________________________________ rsyslog mailing list http://lists.adiscon.net/mailman/listinfo/rsyslog http://www.rsyslog.com/professional-services/ What's up with rsyslog? Follow https://twitter.com/rgerhards NOTE WELL: This is a PUBLIC mailing list, posts are ARCHIVED by a myriad of sites beyond our control. PLEASE UNSUBSCRIBE and DO NOT POST if you DON'T LIKE THAT.
