From: Jérôme P. <ng...@gm...> - 2012-05-31 12:20:44
|
On 05/31/12 20:29, Carsten Haitzler wrote: > On Thu, 31 May 2012 18:28:11 +0900 Jérôme Pinot <ng...@gm...> said: > > > SlackE17, the E17 packaging project for E17 is now based on released > > code. But SVN is still moving and for testing latest code, released > > libraries are not enough. For instance, e doesn't build anymore > > against EFL 1.2 > > > > So, I would like to add SlackBuilds to trunk/packaging/slackware, to > > help Slackware people build and test the SVN version. It's mostly shell > > scripts and text files. Consider this like an unstable and smaller version > > of the build infra of SlackE17. > > > > SlackE17 will, in same time, follow the last stable branch, and provide > > users with binary packages. > > > > Any objection or comment about this addition? > > this is ok - but an alternative is that you just ship the snapshot of e that > was made last efl release. It's more or less what I already do. But good packages need lot of tests and sometimes an SVN revision is better than a release: http://sourceforge.net/projects/slacke17/files/slacke17/ The files that I'm going to commit are for advanced people willing to test svn. It's like an easy_e17.sh script but that goes nicely with the Slackware packaging system. It is not meant for shipping binaries. Actually, I need this myself, because SlackE17 will surely not move till E17 release, and I need to test change very often. I thought it was better to keep this in the trunk for now. >this is pretty much the release model and following > svn is of course going to bring in issues like this. Sometimes, I like to track issues :-) -- Jérôme Pinot http://ngc891.blogdns.net/ |