public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: Jaco Kroon <jaco@uls.co.za>
To: gentoo development <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev] recommendation to last-rite openl2tp
Date: Thu, 11 Jul 2024 10:07:32 +0200	[thread overview]
Message-ID: <274d3ff8-15c8-4cf7-ac51-250ce178c4eb@uls.co.za> (raw)

Hi All,

I noted there has been a recent push to deprecate and clean up the tree 
as much as possible.

Another possible candidate is net-dialup/openl2tp.

We've been using this for a while now, with some recent patches we've 
added against xl2tpd (mostly myself) we now believe there is no longer 
any need for openl2tp.  We've just discontinued it's use on the last two 
sites where we still used it in preference of xl2tpd after patching 
xl2tpd to add the functionality we needed for those two sites (which 
incidentally also wasn't present in openl2tp, from a code perspective 
xl2tp is also simpler to work on, PR will be created on xl2tpd github's 
shortly and update for ::gentoo made).

With this I no longer see any need to carry openl2tp in the tree, and 
happy to file the relevant PRs to last-rite and purge (it's already 
maintainer-wanted) it from the tree entirely.

It has two bugs open, and it does not look like there is any interest to 
fix those (looks like automated reporting).  It would also directly 
close at least one bug on ppp itself (https://bugs.gentoo.org/414901).

Kind regards,
Jaco




             reply	other threads:[~2024-07-11  8:07 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-07-11  8:07 Jaco Kroon [this message]
2024-07-11 10:06 ` [gentoo-dev] recommendation to last-rite openl2tp Matt Jolly

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=274d3ff8-15c8-4cf7-ac51-250ce178c4eb@uls.co.za \
    --to=jaco@uls.co.za \
    --cc=gentoo-dev@lists.gentoo.org \
    /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