David Sommerseth wrote:
> And thank you for getting this into Gentoo!
I agree! And I want to plug Gentoo's overlay system as well, it's
really a fantastic way to allow system customization.
Write ebuilds, commit to any public repo, write a simple .xml file
and then layman can be used on any Gento
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
On 24/02/10 14:24, Marcel Pennewiß wrote:
> Hi,
>
> following the discussions and new patches i adapted the current Gentoo Ebuild
> to use the allmerged-testing-tree (openvpn-.ebuild).
>
> I'll try to keep it working and also i'll try to suppor
Hi,
On Mon, Feb 22, 2010 at 10:41:49PM +0100, David Sommerseth wrote:
> From: David Sommerseth
>
> Added a new function, warn_deprecated_features(), which is located in
> deprecated.[ch]. All deprecated features should present a warning here.
> This function will be called during start-up and w
With some help from the former port maintainer, I've undeleted
security/openvpn-devel in the FreeBSD ports tree and have updated it with a git
pull from last week. My goal is to keep a recent snapshot within the FreeBSD
ports tree, on a weekly or biweekly basis.
Ideally, the version that makes
Hi,
On Wed, Feb 24, 2010 at 02:24:39PM +0100, Marcel Pennewiß wrote:
> following the discussions and new patches i adapted the current Gentoo Ebuild
> to use the allmerged-testing-tree (openvpn-.ebuild).
This is really cool, thanks.
> In march i'll try to setup a full ipv6-setup using Gert
Hi,
following the discussions and new patches i adapted the current Gentoo Ebuild
to use the allmerged-testing-tree (openvpn-.ebuild).
I'll try to keep it working and also i'll try to support the ebuilds on the
openvpn-devel mailinglist ;) The Ebuilds and all associated files can be found
On 02/24/2010 02:36:45 AM, Samuli Seppänen wrote:
>
> >> If someone who explicitly chooses a functionality
> >> needs to get a warning about the default they
> >> should get this warning at ./configure time --
> >> the time they make the choice.
> >>
> >
> > The only time I can think of that
>> If someone who explicitly chooses a functionality
>> needs to get a warning about the default they
>> should get this warning at ./configure time --
>> the time they make the choice.
>>
>
> The only time I can think of that a warning should
> be delivered to those who explicitly choose
>
