Re: [E-devel] Slackware packaging
On Thu, 31 May 2012 21:20:26 +0900 Jérôme Pinot ngc...@gmail.com said: On 05/31/12 20:29, Carsten Haitzler wrote: On Thu, 31 May 2012 18:28:11 +0900 Jérôme Pinot ngc...@gmail.com 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/ sure - if you try svn regularly - build a package set for yourself and test it out for a few days and if its good - publish it. most packagers seem unwilling to do that QA process and just want a release so they don't have to do this :) 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/ -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
[E-devel] Slackware packaging
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? -- Jérôme Pinot http://ngc891.blogdns.net/ signature.asc Description: Digital signature -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Slackware packaging
On Thu, May 31, 2012 at 11:28 AM, Jérôme Pinot ngc...@gmail.com wrote: 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? of course not :) there are visual studio in that dir, so you can put linux scripts files there :) Vincent -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Slackware packaging
Vtorri is right, there are even files for vs there so a bunch of shell scripts for slackware shouldn't/wouldn't/couldn't hurt anyway. It will also be a plus for those who want to have latest EFL for their slack without keeping a private build infra of their own. in other words nice idea! please approve, please proceed :p -- Regards, Alex-P. Natsios (a.k.a Drakevr) -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Slackware packaging
On Thu, 31 May 2012 18:28:11 +0900 Jérôme Pinot ngc...@gmail.com wrote: 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? I thought that's what trunk/packaging was for. So go for it. -- A big old stinking pile of genius that no one wants coz there are too many silver coated monkeys in the world. signature.asc Description: PGP signature -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Slackware packaging
On Thu, 31 May 2012 18:28:11 +0900 Jérôme Pinot ngc...@gmail.com 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. this is pretty much the release model and following svn is of course going to bring in issues like this. -- - Codito, ergo sum - I code, therefore I am -- The Rasterman (Carsten Haitzler)ras...@rasterman.com -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/ ___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
Re: [E-devel] Slackware packaging
On 05/31/12 20:29, Carsten Haitzler wrote: On Thu, 31 May 2012 18:28:11 +0900 Jérôme Pinot ngc...@gmail.com 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/ signature.asc Description: Digital signature -- Live Security Virtual Conference Exclusive live event will cover all the ways today's security and threat landscape has changed and how IT managers can respond. Discussions will include endpoint security, mobile security and the latest in malware threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/___ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
