Util-Linux package development
 help / color / mirror / Atom feed
From: Bruce Dubbs <bruce.dubbs@gmail.com>
To: util-linux@vger.kernel.org
Subject: Re: [PATCH] agetty: Reprompt once the network addresses change if address displayed
Date: Tue, 07 Jul 2015 00:05:38 -0500	[thread overview]
Message-ID: <559B5E22.2050902@gmail.com> (raw)
In-Reply-To: <20150707042512.GI17734@vapier>

Mike Frysinger wrote:
> On 06 Jul 2015 13:58, Bruce Dubbs wrote:
>> Mike Frysinger wrote:
>>> On 03 Jul 2015 14:58, Stef Walter wrote:
>>>     #ifdef AGETTY_RELOAD
>>>>    # include <sys/inotify.h>
>>>> +# include <linux/netlink.h>
>>>> +# include <linux/rtnetlink.h>
>>>
>>> why not use libmnl instead ?
>>> 	http://netfilter.org/projects/libmnl
>>
>> That would not work for the LinuxFromScratch project.  At the time
>> util-linux is built, libmnl is not available.
>
> then update the LFS insns to include libmnl, or build util-linux with the
> reload option disabled.  i don't see how LFS's decisions are relevant here.
> -mike

Yes, we can do either, but it seems like a lot of overhead to add a new 
package for 95 lines of code that are already written.

We already manage about 1000 packages and are volunteers. Many of my 
users would call adding a new library for one minor function bloat.
None of the packages we support now use that library although that could 
change in the future if others start to use it.

Yes, our decisions are only a minor input to upstream packages, but 
there may be others that have similar concerns that don't monitor this list.

   -- Bruce


  reply	other threads:[~2015-07-07  5:05 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-03 12:58 [PATCH] agetty: Reprompt once the network addresses change if address displayed Stef Walter
2015-07-06 14:07 ` Mike Frysinger
2015-07-06 18:58   ` Bruce Dubbs
2015-07-07  4:25     ` Mike Frysinger
2015-07-07  5:05       ` Bruce Dubbs [this message]
2015-07-07  7:07         ` Mike Frysinger
2015-07-07 14:56           ` Bruce Dubbs
2015-07-07 15:56             ` Mike Frysinger
2015-07-09  7:20   ` Stef Walter
2015-07-20  9:26     ` Karel Zak

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=559B5E22.2050902@gmail.com \
    --to=bruce.dubbs@gmail.com \
    --cc=util-linux@vger.kernel.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