Hi Alon,

The spec files I used are originally from RPMforge, forked when
2.3-alpha1 was released. I did not use the openvpn.spec.in file from the
repo as it seemed outdated at the time. Now that I look again at the
history of openvpn.spec.in file, I see that much of it was rewritten
during the buildsystem overhaul:

git diff --follow d02a86...HEAD -- distro/rpm/openvpn.spec.in

I'll see if I could merge my changes with this file and hopefully use
that for the next release.

Regarding Debian packaging... it'd be great if it could be integrated to
the core build (e.g. "make debian"), I just don't have a clue how to do
that using autoconf. In case somebody is willing to do the integration,
a typical Debian build goes currently like this:

$ pwd
/home/user
$ cp -r debian openvpn-<version>/
$ cp changelog openvpn-<version>/debian/
$ cd openvpn-<version>
$ autoreconf -vi
$ dpkg-buildpackage -b

The "debian" directory contains most of the packaging files, which
should be in the root of the openvpn git repo or copied there. The
debian/changelog file could/should be generated by the user prior to the
build. The .deb packages would end up in /home/user.

Unlike RPM .spec files, the debian control file with the package
dependencies etc. does not  accept conditionals. The standard
debian/control file I have works for Debian 6 and Ubuntu 10.04, but a
modified one was needed for Ubuntu 12.04. Some magic is required to
handle this. The rest of the files are identical, at least for now.

I think I'll fork openvpn on GitHub and make my modifications there
before posting any patches to the ml.

Samuli
> Hello Samuli,
>
> Why didn't you use rpmbuild -tb <tarball>.tar.gz?
> And if you have changes in spec file you should probably add this with
> proper conditionals to the spec file within the appropriate package.
>
> There should be no external resource maintained.
>
> The debian packaging should also be integrated within project.
>
> Alon
>
> On Fri, Jul 13, 2012 at 3:22 PM, Samuli Seppänen <sam...@openvpn.net> wrote:
>> Hi all,
>>
>> I've just finished packaging openvpn-2.3_alpha2 for Debian/Ubuntu and
>> Fedora/EL. As the packaging files required significant changes on both
>> Debian and RPM front, I've put them here for others to use/improve:
>>
>> <http://build.openvpn.net/downloads/packaging>
>>
>> The packaging highlights for the 2.3_alpha2 are:
>>
>> - easy-rsa split into it's own architecture-independent package
>> - packages for Ubuntu 12.04
>> - debian packaging files made as generic as possible, only Ubuntu 12.04
>> files having required minor changes
>>
>> CentOS/EL6 is still missing the new packages as I don't have direct
>> access to the CentOS build computers until next Monday. All other
>> packages are already in their respective ("-snapshot") repositories.
>>
>> For details on how to use our software repositories, please look here:
>>
>> <https://community.openvpn.net/openvpn/wiki/OpenvpnSoftwareRepos>
>>
>> If you encounter any issues with the packages, please let me know! Also,
>> any suggestions on where to host these files in the long run are most
>> appreciated! Perhaps "openvpn-build" repository would be the least bad
>> place?
>> --
>> Samuli Seppänen
>> Community Manager
>> OpenVPN Technologies, Inc
>>
>> irc freenode net: mattock
>>
>> ------------------------------------------------------------------------------
>> 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/
>> _______________________________________________
>> Openvpn-devel mailing list
>> Openvpn-devel@lists.sourceforge.net
>> https://lists.sourceforge.net/lists/listinfo/openvpn-devel


Reply via email to