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.
