Mailing List Archive: Linux-HA: Dev

configure.in kludge

Index | Next | Previous | View Threaded

abeekhof at suse

Feb 28, 2007, 8:54 AM

Post #1 of 8 (785 views)
Permalink

configure.in kludge

Alan,

can you please explain the reason for the kludge you added in the
following configure block

AC_MSG_CHECKING(for special snmp libraries)
SNMPLIB=`net-snmp-config --libs`
SNMPAGENTLIB=`net-snmp-config --agent-libs`
# KLUDGE!!
case $SNMPAGENTLIB in
*wrap*) ;;
*) SNMPAGENTLIB="$SNMPAGENTLIB -lwrap";;
esac
AC_MSG_RESULT($SNMPLIB)

I ask because it prevents building when -lwrap is not present.
It seems odd that we apparently think we know more than the people
that publish the snmp package.

--
Andrew Beekhof

SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)

_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev[at]lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

alanr at unix

Mar 1, 2007, 10:31 PM

Post #2 of 8 (753 views)
Permalink

Re: configure.in kludge [In reply to]

Andrew Beekhof wrote:
> Alan,
>
> can you please explain the reason for the kludge you added in the
> following configure block
>
> AC_MSG_CHECKING(for special snmp libraries)
> SNMPLIB=`net-snmp-config --libs`
> SNMPAGENTLIB=`net-snmp-config --agent-libs`
> # KLUDGE!!
> case $SNMPAGENTLIB in
> *wrap*) ;;
> *) SNMPAGENTLIB="$SNMPAGENTLIB -lwrap";;
> esac
> AC_MSG_RESULT($SNMPLIB)
>
> I ask because it prevents building when -lwrap is not present.
> It seems odd that we apparently think we know more than the people that
> publish the snmp package.

Because SUSE didn't include the full set of dependencies, and I wanted
it to work.

The other option is have it not work, which I thought wasn't quite as
good an option.

--
Alan Robertson <alanr[at]unix.sh>

"Openness is the foundation and preservative of friendship... Let me
claim from you at all times your undisguised opinions." - William
Wilberforce
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev[at]lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

beekhof at gmail

Mar 2, 2007, 12:07 AM

Post #3 of 8 (760 views)
Permalink

Re: configure.in kludge [In reply to]

On 3/2/07, Alan Robertson <alanr[at]unix.sh> wrote:
> Andrew Beekhof wrote:
> > Alan,
> >
> > can you please explain the reason for the kludge you added in the
> > following configure block
> >
> > AC_MSG_CHECKING(for special snmp libraries)
> > SNMPLIB=`net-snmp-config --libs`
> > SNMPAGENTLIB=`net-snmp-config --agent-libs`
> > # KLUDGE!!
> > case $SNMPAGENTLIB in
> > *wrap*) ;;
> > *) SNMPAGENTLIB="$SNMPAGENTLIB -lwrap";;
> > esac
> > AC_MSG_RESULT($SNMPLIB)
> >
> > I ask because it prevents building when -lwrap is not present.
> > It seems odd that we apparently think we know more than the people that
> > publish the snmp package.
>
> Because SUSE didn't include the full set of dependencies,

did it get reported/fixed? if not we should do so.

> and I wanted it to work.
> The other option is have it not work, which I thought wasn't quite as
> good an option.

i figured there was some reason, i just didnt know what it was.
i might go update configure so the next person that looks knows too
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev[at]lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

alanr at unix

Mar 2, 2007, 5:53 AM

Post #4 of 8 (754 views)
Permalink

Re: configure.in kludge [In reply to]

Andrew Beekhof wrote:
> On 3/2/07, Alan Robertson <alanr[at]unix.sh> wrote:
>> Andrew Beekhof wrote:
>> > Alan,
>> >
>> > can you please explain the reason for the kludge you added in the
>> > following configure block
>> >
>> > AC_MSG_CHECKING(for special snmp libraries)
>> > SNMPLIB=`net-snmp-config --libs`
>> > SNMPAGENTLIB=`net-snmp-config --agent-libs`
>> > # KLUDGE!!
>> > case $SNMPAGENTLIB in
>> > *wrap*) ;;
>> > *) SNMPAGENTLIB="$SNMPAGENTLIB -lwrap";;
>> > esac
>> > AC_MSG_RESULT($SNMPLIB)
>> >
>> > I ask because it prevents building when -lwrap is not present.
>> > It seems odd that we apparently think we know more than the people that
>> > publish the snmp package.
>>
>> Because SUSE didn't include the full set of dependencies,
>
> did it get reported/fixed? if not we should do so.

Almost certainly didn't get reported by me.

>> and I wanted it to work.
>> The other option is have it not work, which I thought wasn't quite as
>> good an option.
>
> i figured there was some reason, i just didnt know what it was.
> i might go update configure so the next person that looks knows too

It was _soo_ obviously a kludge I thought it would be obvious that it
was necessary for someone ;-) (that's the kind of thinking I sometimes
fall into when in a hurry). I was in the middle of putting out a
release, and found this on only one platform IIRC. I don't remember
which one, but it was definitely SUSE. Probably SUSE 10.0 or 10.1. I'm
guessing SUSE 10.0. Probably could tell by the date I made the change.

--
Alan Robertson <alanr[at]unix.sh>

"Openness is the foundation and preservative of friendship... Let me
claim from you at all times your undisguised opinions." - William
Wilberforce
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev[at]lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

lmb at suse

Mar 2, 2007, 7:07 AM

Post #5 of 8 (753 views)
Permalink

Re: configure.in kludge [In reply to]

On 2007-03-02T06:53:05, Alan Robertson <alanr[at]unix.sh> wrote:

> > i figured there was some reason, i just didnt know what it was.
> > i might go update configure so the next person that looks knows too
>
> It was _soo_ obviously a kludge I thought it would be obvious that it
> was necessary for someone ;-) (that's the kind of thinking I sometimes
> fall into when in a hurry). I was in the middle of putting out a
> release, and found this on only one platform IIRC. I don't remember
> which one, but it was definitely SUSE. Probably SUSE 10.0 or 10.1. I'm
> guessing SUSE 10.0. Probably could tell by the date I made the change.

Unlikely to get fixed for 10.0 (if it was that dist, didn't verify) and
10.1/SLES10 and up are correct.

If you'd ask me, I'd drop the kludge because I no longer care about
anything that old for newer versions ;-)

--
Teamlead Kernel, SuSE Labs, Research and Development
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
"Experience is the name everyone gives to their mistakes." -- Oscar Wilde

_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev[at]lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

alanr at unix

Mar 2, 2007, 8:58 AM

Post #6 of 8 (756 views)
Permalink

Re: configure.in kludge [In reply to]

Lars Marowsky-Bree wrote:
> On 2007-03-02T06:53:05, Alan Robertson <alanr[at]unix.sh> wrote:
>
>>> i figured there was some reason, i just didnt know what it was.
>>> i might go update configure so the next person that looks knows too
>> It was _soo_ obviously a kludge I thought it would be obvious that it
>> was necessary for someone ;-) (that's the kind of thinking I sometimes
>> fall into when in a hurry). I was in the middle of putting out a
>> release, and found this on only one platform IIRC. I don't remember
>> which one, but it was definitely SUSE. Probably SUSE 10.0 or 10.1. I'm
>> guessing SUSE 10.0. Probably could tell by the date I made the change.
>
> Unlikely to get fixed for 10.0 (if it was that dist, didn't verify) and
> 10.1/SLES10 and up are correct.
>
> If you'd ask me, I'd drop the kludge because I no longer care about
> anything that old for newer versions ;-)

I suppose we ought to at least putting the date into text so we can
expire these out once they've been fixed for a few years.

--
Alan Robertson <alanr[at]unix.sh>

"Openness is the foundation and preservative of friendship... Let me
claim from you at all times your undisguised opinions." - William
Wilberforce
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev[at]lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

lmb at suse

Mar 3, 2007, 3:02 AM

Post #7 of 8 (757 views)
Permalink

Re: configure.in kludge [In reply to]

On 2007-03-02T09:58:31, Alan Robertson <alanr[at]unix.sh> wrote:

> I suppose we ought to at least putting the date into text so we can
> expire these out once they've been fixed for a few years.

Well, SCMs are pretty good at telling such dates.

I was really just riding my pet peeve of supporting age old
distributions instead of having a coherent tip across the entire OS to
update to, w/o needing to do legacy kludges. An issue I have which very
clearly not only is restricted to heartbeat. ;-)

_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev[at]lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

alanr at unix

Mar 3, 2007, 7:21 AM

Post #8 of 8 (751 views)
Permalink

Re: configure.in kludge [In reply to]

Lars Marowsky-Bree wrote:
> On 2007-03-02T09:58:31, Alan Robertson <alanr[at]unix.sh> wrote:
>
>> I suppose we ought to at least putting the date into text so we can
>> expire these out once they've been fixed for a few years.
>
> Well, SCMs are pretty good at telling such dates.
>
> I was really just riding my pet peeve of supporting age old
> distributions instead of having a coherent tip across the entire OS to
> update to, w/o needing to do legacy kludges. An issue I have which very
> clearly not only is restricted to heartbeat. ;-)

HA customers are notoriously slow to change things that are working, and
often have machines that are up for years at a time. I think that we
need to avoid breaking things for 3-5 years. Beyond 5 years, I probably
don't care. But, NOT 18 months. That's not the same as saying Novell
or whoever will provide support such things, but there's no compelling
reason to break them either.

In addition, as you have pointed out to me on other topics, I think we
have more important issues to worry about.

--
Alan Robertson <alanr[at]unix.sh>

"Openness is the foundation and preservative of friendship... Let me
claim from you at all times your undisguised opinions." - William
Wilberforce
_______________________________________________________
Linux-HA-Dev: Linux-HA-Dev[at]lists.linux-ha.org
http://lists.linux-ha.org/mailman/listinfo/linux-ha-dev
Home Page: http://linux-ha.org/

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com