Development discussion of WireGuard
 help / color / mirror / Atom feed
From: Egbert Verhage <egbert@eggiecode.org>
To: Anonymous Anonymous <admin@hda.me>
Cc: WireGuard mailing list <wireguard@lists.zx2c4.com>
Subject: Re: [WireGuard] Wireguard package, changed naming
Date: Fri, 18 Nov 2016 13:42:46 +0100	[thread overview]
Message-ID: <be6d4bdc-1af6-7f3d-d732-6a7dea586da1@eggiecode.org> (raw)
In-Reply-To: <1587734ccf8.f42077433014.7510260495499425564@hda.me>

[-- Attachment #1: Type: text/plain, Size: 1614 bytes --]

Hey ?,

First of if you want to change something to the PPA, what is public and 
advertised on the website, make it public. In de mailing list and to me.

I'm fine with the change of ubuntu suffix to wg.
ifupdown packages is included to add wireguard network/interfaces. 
Usefull if you are using a ansible to deploying on multiple machine.

I never used bzr, that is the reason why I use git. To setup the repo 
multiple for distros just use git branches.
The code is in git: https://git.launchpad.net/wireguard, and is uses git 
submodule for the wireguard source. Then you just checkout the lastest 
snapshot and change the changelog and commit,push that.

If you are subscribed to the mailing list of wireguard, then you get an 
email that there is a new snapshot available.

Greetz,
Egbert

On 2016-11-18 12:31, Anonymous Anonymous wrote:
> I changed wireguard package naming from ubuntu1 to wg1, hope you not 
> against it. Since only ubuntu official repository packages could be 
> with ubuntu naming.
> And we don't need libmnl dependency, only libmnl-dev.
> As for ifupdown, I have no idea what it doing in PPA. Is there some 
> issues with wireguard regarding ifupdown?
> And, I have no access to bzr, but I don't use since its auto-importing 
> from git, when commits sign broken anyway. I figured what you talked 
> about change maintainer, you was talking about launchpad team, not a PPA.
>  I changed both maintainer and driver to teamname itself.
> P.S.: I included your email for snapshot tags in my email bot 
> settings. It just send notification when new version (snapshot in our 
> case) out.


[-- Attachment #2: Type: text/html, Size: 2824 bytes --]

           reply	other threads:[~2016-11-18 12:40 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <1587734ccf8.f42077433014.7510260495499425564@hda.me>]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=be6d4bdc-1af6-7f3d-d732-6a7dea586da1@eggiecode.org \
    --to=egbert@eggiecode.org \
    --cc=admin@hda.me \
    --cc=wireguard@lists.zx2c4.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).