Re: On the nature of backward comparability

2018-05-31 Thread Wes Hardaker via Net-snmp-coders
Bart Van Assche writes: > The Linux kernel uses a similar but more complex approach. Net-SNMP is > the only software project I know of that has information about which > files should be built embedded in source code files instead of in (the > equivalent of) makefiles. The rational for this stems

Re: On the nature of backward comparability

2018-05-15 Thread Bart Van Assche
On 05/15/18 17:41, Magnus Fromreide wrote: One other issue with --enable-minimalist is that it is kind of broken since it requires that you pass information back from the agent building pass to the lib building pass and from the mib pass to the agent pass but that happens to late. I have been toy

Re: On the nature of backward comparability

2018-05-15 Thread Magnus Fromreide
On Tue, May 15, 2018 at 08:33:20AM -0700, Wes Hardaker via Net-snmp-coders wrote: > Bart Van Assche writes: > > > Is there perhaps a list available of the MIBs that are compatible with > > --enable-read-only, --enable-mini-agent and --enable-minimalist? > > They all do different things: > > 1)

Re: On the nature of backward comparability

2018-05-15 Thread Keith Mendoza
On Tue, May 15, 2018, at 12:58 PM, Wes Hardaker wrote: > Keith Mendoza writes: > > > Now that development is going to be done on github, what I would > > recommend is forking from the official net-snmp and then maybe create > > a branch on your github fork. > > Why do you think that's better t

Re: On the nature of backward comparability

2018-05-15 Thread Wes Hardaker via Net-snmp-coders
Keith Mendoza writes: > Now that development is going to be done on github, what I would > recommend is forking from the official net-snmp and then maybe create > a branch on your github fork. Why do you think that's better than submitting it as a branch within the offical fork? Just to reduce

Re: On the nature of backward comparability

2018-05-15 Thread Keith Mendoza
Wes On Mon, May 14, 2018, at 4:40 PM, Wes Hardaker via Net-snmp-coders wrote: > > We (my last employee) received a patch from a company that implemented a > cmake build system for some percentage of the code. It was better in > many ways and had issues in others as it was a different form of >

Re: On the nature of backward comparability

2018-05-15 Thread Wes Hardaker via Net-snmp-coders
Bill Fenner writes: > And it constantly breaks (it's broken again in master), this time in > mib modules that I don't use so only noticed when I started poking at > the travis results because of Bart's report about snmpping. We need a set of continual build tests, as also mentioned in that messa

Re: On the nature of backward comparability

2018-05-15 Thread Bill Fenner
On Tue, May 15, 2018 at 11:33 AM, Wes Hardaker via Net-snmp-coders < net-snmp-coders@lists.sourceforge.net> wrote: > 3) --enable-minimalist is an interesting one that is also designed for >code reduction in that one section of code can declare the need for a >function, and if and only if t

Re: On the nature of backward comparability

2018-05-15 Thread Wes Hardaker via Net-snmp-coders
Bart Van Assche writes: > Is there perhaps a list available of the MIBs that are compatible with > --enable-read-only, --enable-mini-agent and --enable-minimalist? They all do different things: 1) --enable-read-only has been around longer than snmpping.c, and it's clear that the person that

Re: On the nature of backward comparability

2018-05-15 Thread Bart Van Assche
On 05/14/18 14:07, Wes Hardaker via Net-snmp-coders wrote: [Note that with all the above, we also had to deal with the desire to keep SNMP code stacks small. We still get requests for people that don't want any openssl code in their compiled system because auditing is worse, and --enable-mini-ag

Re: On the nature of backward comparability

2018-05-14 Thread Keith Mendoza
Wes, Thank you for taking the time to put the history of Net-SNMP's codebase to paper. I feel that it puts why the codebase is the way it is in its proper perspective. After reading this very insightful essay, I feel that Net-SNMP being the "de-facto SNMP stack" also means that it's the refere

Re: On the nature of backward comparability

2018-05-14 Thread Wes Hardaker via Net-snmp-coders
Bart Van Assche writes: >> A) write a configure test for any struct/api/feature/etc that wasn't >> portable across all platforms. >> >> B) failing the ability to do that, see if you could determine it at >> runtime (see agent/auto_nlist as a reference point). >> >> C) Failing that, create

Re: On the nature of backward comparability

2018-05-14 Thread Bart Van Assche
Thanks Wes for the elaborate write-up. On 05/14/18 14:07, Wes Hardaker via Net-snmp-coders wrote: The struggle with all of this, of course, is that the code begins to look a little crusty in spots while we try to maintain support for so many operating systems that we don't even have the ability

On the nature of backward comparability

2018-05-14 Thread Wes Hardaker via Net-snmp-coders
[hopefully mostly coherent rambling below?] This is more of a "history of where we are and how we got here" than a directive. But it's important we consider how we got here before making major changes to the code base, especially surrounding changes that break backward compatibility. Long long