new ppp release ?

[joakim-tjernlund]

The last ppp release was quite some time ago. Is a new one forthcoming ?

[hansfn]

Yes, a new release is very much needed - ppp no longer compiles on Gentoo.

This has been fixed in commit 3c7b862 - "pppd: Use openssl for the DES instead of the libcrypt / glibc".

Please consider creating a new release ASAP.

[kloczek]

Yes, a new release is very much needed - ppp no longer compiles on Gentoo.

Part of the problems of the ppp as the project is completely crappy and custom made set of makefiles and custom configure script.
It would be good to move to even autoconf/automake/libtool.
It would be good to know it that kind of ppp improvements would be welcome by maintainer or not.

[Neustradamus]

+1 (since 2014)

Note: There are patches here: https://www.nikhef.nl/~janjust/ppp/

Please look this ticket: #131

EDIT : Merged, good job @jjkeijser!

[kloczek]

I'm begging to make new ppp release :/

[Neustradamus]

@paulusmack, @joakim-tjernlund, @hansfn, @kloczek: What do you think for an official perfect build?

[joakim-tjernlund]

A release would be great but seems like github is not the place Paulus wants to discuss, see
347904e

[paulusmack]

Right. I do prefer mailing lists (i.e. the linux-ppp@vger.kernel.org list).

However, since we're here, do you all think the tree in its current state is releaseable, or are there things that must be fixed before release?

[kloczek]

Paul,

Please understand that asking to subscribe on mailing list to ask the question is kind of overkill.

Mailing lists are OK in case of long term commitment to join the project. For anything else github issue tickets are all what is needed.
Many github projects already abandoned even mailing list and they are using issues tickets as topics to discuss.
You can have look on https://github.com/att/ast/issues/ to see how it works.
It is better because it allows automatically connect discussions with already submitted patches, tickets or content of the projects (if github module has entries in projects tab).
Using that way everything is easy to track and additionally in one place.

[kloczek]

So going back to the subject: do you have any plans to make new release soon? :)

[Neustradamus]

@paulusmack: The list is a big mess...

Can you look for integrate patches here too? https://www.nikhef.nl/~janjust/ppp/

Please look this ticket: #131

EDIT : Merged, good job @jjkeijser!

[paulusmack]

@paulusmack: The list is a big mess...

What list? The mailing list, or are you referring to some list of patches, or some other list?

Can you look for integrate patches here too? https://www.nikhef.nl/~janjust/ppp/

That's rather large. I would need a signoff at least. I would also want James Carlson to review and ack it. Please post it to linux-ppp (with a Signed-off-by, and a From: line if you are not the author) so he sees it. Please also consider splitting it, if that would make a series of logical steps that are easier to review.

[paulusmack]

It would be good to move to even autoconf/automake/libtool.

Puke. My experience of autoconf/automake has been that their output is verbose, unreadable and undebuggable. For a small project like ppp that only supports Linux and Solaris there isn't a lot that needs to be configured, so I prefer something that's simple and direct and understandable.

[paulusmack]

So going back to the subject: do you have any plans to make new release soon? :)

Yes, I would like to make a new release soon. The question is whether I just release what's in the tree now, or if there are some patches that are really needed before release.

[lygstate]

@paulusmack I suggest release a version first, and then bugfixes it

[paulusmack]

I propose to release the tree as it currently is (plus updates to README and pppd/patchlevel.h) as ppp-2.4.8 shortly.