file config.h.in should be ignored

[icegood]

Should it be ignored?
https://github.com/ppp-project/ppp/blob/master/pppd/plugins/pppoe/config.h.in

[Neustradamus]

@paulusmack, @enaess: Have you seen this issue?

[enaess]

IIRC the config.h is still generated for pppoe. It's a weird project organization where pppoe should probably have its own sub-configure task or be moved to a separate repository. I died on that hill a while back ...

[icegood]

OK, so we have something in code that autotools are not managed to solve. Could you explain in details what is it, since i'm not familar with autotools deep inside?
BTW, strange decision to move to autotools. I think, cmake would be more convenient in this regard...

[enaess]

@icegood what is the problem you are trying to resolve?

You have many good solutions for building a project, autotools is just one of them. Cmake is mostly a C++ based tool, and mason is another good (and more recent) one. Whichever set of tools we stick with has it's pros/cons, but it was still mile-high better than the hard-coded configure script that was checked in.

[enaess]

It's just that this repository has traditionally been a "mono-repository" where all build dependencies was checked in, in one way or another (e.g. libfreeradius, libatm), then also tried to build individual projects like pppoe-plugin, etc. If I had my way, I'd spin out the pppoe plugin in a separate repository and use autotools (or whatever else deemed good at the time to build the sources).

[Neustradamus]

@icegood: Have you seen latest comments?