Hi, Rainer and I discussed how we could best change the current build scripts for automatic processing.
Right now, there are two different approaches: 1. The script for the daily builds have the branch and platform pre-configured in the script and don't need a changelog entry, because daily builds are purely experimental. 2. The script for regular releases currently needs some input. First the repack.sh script needs to be run and after that the uploadppa.sh script which actually prepares the files. In the second script I also need to select the tarball, branch and platform to build. Also the package changelog needs to be entered manually. Thus, I need to run the script multiple times. Basically, release packages should be built just the same as daily packages, with as little manual interaction as possible. The scripts for daily packages already proved that it is not too complicated to let the build run with different parameters, leaving the changelog being the problem. The problem right now is, that we do not know how to approach this the best way. Currently, the package changelog is generated via dch, but this has to be done for each different platform. My thought was to have a single changelog file, which then has the upstream release version automatically generated (currently done "manually" via dch). Are there other ways of doing this? Is there a way to achieve the desired automization? Ideas and suggestions are very welcome. Florian _______________________________________________ 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.
