Re: [Openvpn-devel] Packaging OpenVPN for various platforms?
On Thu, Jul 01, 2010 at 11:29:29AM -0500, Eric F Crist wrote: > This will not work for freebsd. This is what the ports tree is for. same goes for OpenBSD. felix > > Eric > > > On Jul 1, 2010, at 09:59:51, Till Maas wrote: > > > On Wed, Jun 30, 2010 at 12:00:49PM +0300, Samuli Seppänen wrote: > > > >> - write packaging instructions to our Trac wiki > >> (https://community.openvpn.net/openvpn/wiki) > >> - convert the instructions into BuildBot code (BuildSteps) > >> > >> After this is done, we can provide the latest version of OpenVPN for > >> various platforms with minimal manual effort. This helps developers as > >> well as users: having the development code in wider circulation helps > >> spot problems faster resulting in faster release cycle. > > > > I am a Fedora package maintainer, but not one of OpenVPN. I CC'ed them > > in case they did not notice this. > > > > The Fedora package scripts are currently available here: > > http://cvs.fedoraproject.org/viewvc/rpms/openvpn/devel/ > > > > In the not so far future this URL will not be valid, because Fedora > > switches to git. > > > > Packages for Fedora are usually build within a chroot using a helper > > tool called mock[0] and I do not know how well it works on other > > distributions except Fedora or RHEL/CentOS. There are also scripts > > developed to easily build new rpms from SCM and afaik currently only git > > is supported (I do not know what OpenVPN currently uses, but I suspect > > it's SVN): > > https://fedorahosted.org/fedora-packager/ticket/8 > > > > Adding support for SVN or other SCMs should not be that hard. I will try > > to write something up how to put all this together to easily build new > > OpenVPN Packages for Fedora using a SCM checkout. > > > > Regards > > Till > > > > [0] http://fedoraproject.org/wiki/Projects/Mock > > -- > > This SF.net email is sponsored by Sprint > > What will you do first with EVO, the first 4G phone? > > Visit sprint.com/first -- > > http://p.sf.net/sfu/sprint-com-first___ > > Openvpn-devel mailing list > > Openvpn-devel@lists.sourceforge.net > > https://lists.sourceforge.net/lists/listinfo/openvpn-devel > > --- > Eric Crist > > > > > > -- > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first > ___ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel -- bytemine GmbH - Entwicklungsmanufaktur fuer innovative Loesungen Geschaeftsfuehrer: Felix Kronlage Marie-Curie-Str. 1 / 26129 Oldenburg Tel: (+49)(0)441 - 309197-0 Fax: (+49)(0)441 - 309197-99 http://www.bytemine.net/ - i...@bytemine.net AG Oldenburg - HRB 203940 VAT-Number: DE267286778 Felix Kronlage - kronl...@bytemine.net - FKR-RIPE Kommunikation gerne mit GPG/PGP: 0xD9AC74D0 Neuigkeiten aus der Datenmine: http://blog.bytemine.net/ signature.asc Description: Digital signature
Re: [Openvpn-devel] Packaging OpenVPN for various platforms?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 01/07/10 17:28, Till Maas wrote: > On Thu, Jul 01, 2010 at 05:21:39PM +0200, David Sommerseth wrote: > >> But, I do see one big advantage of building packages via Koji (Fedora's >> building system which uses mock), if possible. That will put these >> packages into a yum repository almost instantly, which can be useful to >> make the packages more easily available. > > Using koji is a bit of overkill. There is a small perl wrapper that can > be used to easily build a src.rpm for different archs and distributions > called smock: > > http://git.annexia.org/?p=fedora-mingw.git;a=history;f=smock;hb=966f55f8692da3f842da077e57c22ff501e380e1 > > It also creates yum repos with the resulting RPMs. > Ahh, I didn't know about smock, that might as well be an alternative. Yeah, I can agree that koji itself is probably overkill for this kind of routine task. It was more if there were some kind of interfaces we could use. Just to avoid setting up a separate build slave for Fedora/EPEL builds but use what's already publicly available. But I'm advocating for the simplest solution for all of us :) kind regards, David Sommerseth -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkws1oIACgkQDC186MBRfrqYPACgm9rzl0tw2HRR8g1VdXWjJjLw AzoAn3rNifpzOr7ymk3iYtJLJEWRabWn =8Af4 -END PGP SIGNATURE-
Re: [Openvpn-devel] Packaging OpenVPN for various platforms?
This will not work for freebsd. This is what the ports tree is for. Eric On Jul 1, 2010, at 09:59:51, Till Maas wrote: > On Wed, Jun 30, 2010 at 12:00:49PM +0300, Samuli Seppänen wrote: > >> - write packaging instructions to our Trac wiki >> (https://community.openvpn.net/openvpn/wiki) >> - convert the instructions into BuildBot code (BuildSteps) >> >> After this is done, we can provide the latest version of OpenVPN for >> various platforms with minimal manual effort. This helps developers as >> well as users: having the development code in wider circulation helps >> spot problems faster resulting in faster release cycle. > > I am a Fedora package maintainer, but not one of OpenVPN. I CC'ed them > in case they did not notice this. > > The Fedora package scripts are currently available here: > http://cvs.fedoraproject.org/viewvc/rpms/openvpn/devel/ > > In the not so far future this URL will not be valid, because Fedora > switches to git. > > Packages for Fedora are usually build within a chroot using a helper > tool called mock[0] and I do not know how well it works on other > distributions except Fedora or RHEL/CentOS. There are also scripts > developed to easily build new rpms from SCM and afaik currently only git > is supported (I do not know what OpenVPN currently uses, but I suspect > it's SVN): > https://fedorahosted.org/fedora-packager/ticket/8 > > Adding support for SVN or other SCMs should not be that hard. I will try > to write something up how to put all this together to easily build new > OpenVPN Packages for Fedora using a SCM checkout. > > Regards > Till > > [0] http://fedoraproject.org/wiki/Projects/Mock > -- > This SF.net email is sponsored by Sprint > What will you do first with EVO, the first 4G phone? > Visit sprint.com/first -- > http://p.sf.net/sfu/sprint-com-first___ > Openvpn-devel mailing list > Openvpn-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/openvpn-devel --- Eric Crist
Re: [Openvpn-devel] Packaging OpenVPN for various platforms?
On Thu, Jul 01, 2010 at 05:21:39PM +0200, David Sommerseth wrote: > But, I do see one big advantage of building packages via Koji (Fedora's > building system which uses mock), if possible. That will put these > packages into a yum repository almost instantly, which can be useful to > make the packages more easily available. Using koji is a bit of overkill. There is a small perl wrapper that can be used to easily build a src.rpm for different archs and distributions called smock: http://git.annexia.org/?p=fedora-mingw.git;a=history;f=smock;hb=966f55f8692da3f842da077e57c22ff501e380e1 It also creates yum repos with the resulting RPMs. Regards Till pgpGqS5jhFQ2R.pgp Description: PGP signature
Re: [Openvpn-devel] Packaging OpenVPN for various platforms?
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 (Adding the Fedora OpenVPN package maintainer, Steven Pritchard, on Cc.) On 01/07/10 16:59, Till Maas wrote: > On Wed, Jun 30, 2010 at 12:00:49PM +0300, Samuli Seppänen wrote: > >> - write packaging instructions to our Trac wiki >> (https://community.openvpn.net/openvpn/wiki) >> - convert the instructions into BuildBot code (BuildSteps) >> >> After this is done, we can provide the latest version of OpenVPN for >> various platforms with minimal manual effort. This helps developers as >> well as users: having the development code in wider circulation helps >> spot problems faster resulting in faster release cycle. > > I am a Fedora package maintainer, but not one of OpenVPN. I CC'ed them > in case they did not notice this. > > The Fedora package scripts are currently available here: > http://cvs.fedoraproject.org/viewvc/rpms/openvpn/devel/ > > In the not so far future this URL will not be valid, because Fedora > switches to git. > > Packages for Fedora are usually build within a chroot using a helper > tool called mock[0] and I do not know how well it works on other > distributions except Fedora or RHEL/CentOS. There are also scripts > developed to easily build new rpms from SCM and afaik currently only git > is supported (I do not know what OpenVPN currently uses, but I suspect > it's SVN): The openvpn-testing repository is git based, but the coming beta2.2 will be primarily SVN where the -testing repository will mirror the SVN branch. All community patches will go in to the SVN tree via the git tree. > https://fedorahosted.org/fedora-packager/ticket/8 > > Adding support for SVN or other SCMs should not be that hard. I will try > to write something up how to put all this together to easily build new > OpenVPN Packages for Fedora using a SCM checkout. As the building in this context is mostly oriented around the -testing tree, I think you don't need to think too much about SVN support now. The git support should be sufficient. We're looking for a way how to provide openvpn-testing packages for a vast majority of distributions and OSes, to check that it compiles well and to provide binaries for those wanting to be experimental. But, I do see one big advantage of building packages via Koji (Fedora's building system which uses mock), if possible. That will put these packages into a yum repository almost instantly, which can be useful to make the packages more easily available. Steven: I'd like to hear your thoughts on this as well! kind regards, David Sommerseth -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.10 (GNU/Linux) Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org/ iEYEARECAAYFAkwssoAACgkQDC186MBRfrq6uwCdFCtKQQWKoHG5PxouIqkZZvaK Si4An0uK61otB9SuPRiGKKRRY5imId3y =eMvc -END PGP SIGNATURE-
Re: [Openvpn-devel] Packaging OpenVPN for various platforms?
On Wed, Jun 30, 2010 at 12:00:49PM +0300, Samuli Seppänen wrote: > - write packaging instructions to our Trac wiki > (https://community.openvpn.net/openvpn/wiki) > - convert the instructions into BuildBot code (BuildSteps) > > After this is done, we can provide the latest version of OpenVPN for > various platforms with minimal manual effort. This helps developers as > well as users: having the development code in wider circulation helps > spot problems faster resulting in faster release cycle. I am a Fedora package maintainer, but not one of OpenVPN. I CC'ed them in case they did not notice this. The Fedora package scripts are currently available here: http://cvs.fedoraproject.org/viewvc/rpms/openvpn/devel/ In the not so far future this URL will not be valid, because Fedora switches to git. Packages for Fedora are usually build within a chroot using a helper tool called mock[0] and I do not know how well it works on other distributions except Fedora or RHEL/CentOS. There are also scripts developed to easily build new rpms from SCM and afaik currently only git is supported (I do not know what OpenVPN currently uses, but I suspect it's SVN): https://fedorahosted.org/fedora-packager/ticket/8 Adding support for SVN or other SCMs should not be that hard. I will try to write something up how to put all this together to easily build new OpenVPN Packages for Fedora using a SCM checkout. Regards Till [0] http://fedoraproject.org/wiki/Projects/Mock pgplOb9v35LzI.pgp Description: PGP signature
Re: [Openvpn-devel] Packaging OpenVPN for various platforms?
On 30-Jun-10, at 5:00 AM, Samuli Seppänen wrote: Hi all, As some of you may know, I've been building a Buildbot (http://buildbot.net/trac) instance for us. In a nutshell, Buildbot provides several services: - continous integration: inform devs about build failures with arbitrary number of build OSes / configurations - automated packaging: create source tarballs and packages (e.g. Debian, Redhat) from each build, every night etc. - publishing the latest tarballs and packages with help from external apps (apache, yum/apt/ports) I got the basic build process (autoreconf -vi && ./configure && make) working in BuildBot already. Now I'd need help with packaging OpenVPN for various OSes. If you package OpenVPN I'd appreciate a lot if could contact me. For OS X, I have a packaging script here: http://telegraphics.com.au/svn/openvpn-package/trunk/ --Toby My plan is this: - write packaging instructions to our Trac wiki (https://community.openvpn.net/openvpn/wiki) - convert the instructions into BuildBot code (BuildSteps) After this is done, we can provide the latest version of OpenVPN for various platforms with minimal manual effort. This helps developers as well as users: having the development code in wider circulation helps spot problems faster resulting in faster release cycle. Thanks in advance, -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock -- This SF.net email is sponsored by Sprint What will you do first with EVO, the first 4G phone? Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first ___ Openvpn-devel mailing list Openvpn-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-devel
[Openvpn-devel] Packaging OpenVPN for various platforms?
Hi all, As some of you may know, I've been building a Buildbot (http://buildbot.net/trac) instance for us. In a nutshell, Buildbot provides several services: - continous integration: inform devs about build failures with arbitrary number of build OSes / configurations - automated packaging: create source tarballs and packages (e.g. Debian, Redhat) from each build, every night etc. - publishing the latest tarballs and packages with help from external apps (apache, yum/apt/ports) I got the basic build process (autoreconf -vi && ./configure && make) working in BuildBot already. Now I'd need help with packaging OpenVPN for various OSes. If you package OpenVPN I'd appreciate a lot if could contact me. My plan is this: - write packaging instructions to our Trac wiki (https://community.openvpn.net/openvpn/wiki) - convert the instructions into BuildBot code (BuildSteps) After this is done, we can provide the latest version of OpenVPN for various platforms with minimal manual effort. This helps developers as well as users: having the development code in wider circulation helps spot problems faster resulting in faster release cycle. Thanks in advance, -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
