Util-Linux package development
 help / color / mirror / Atom feed
From: bryanh@giraffe-data.com (Bryan Henderson)
To: kzak@redhat.com
Cc: ethanol@armory.com, ams@gnu.org, P@draigbrady.com,
	acahalan@gmail.com, util-linux-ng@vger.kernel.org
Subject: Re: splitting util-linux (was: kill)
Date: 22 Dec 2006 06:44:21 +0000	[thread overview]
Message-ID: <42767.bryanh@giraffe-data.com> (raw)
In-Reply-To: <20061221215312.GP5971@petra.dvoda.cz> (kzak@redhat.com)

> That's not 100% true. You need upstream and downstream maintainer for
> every package. You need an infrastructure (scm, mailing list, ...)
> for every package. Maybe it seems like something simple (10 clicks at
> sf.net), but my experience is completely different. Maintainig is
> really boring work and after few months nobody wants to do it... 
> 
> Number of well maintained packages is not so big. Believe me, people
> who work on Linux distributions fight with unmaintained projects every
> day.

If you're willing to do all that work for all of the components of
util-linux, or alternatively if most of the components simply don't
require any maintenance, then the labor-distributing advantage of
splitting isn't there.  And you've obviously determined that you can
distribute one big package more easily than lots of little ones
(myself, I've found the opposite -- I split things up into independent
parts so that I can release in smaller doses).

That still leaves the flexibility hit for users, since it's extra work
to install just what you want or upgrade just one piece without
disturbing other pieces.

But never mind.  I brought it up in case you had thoughts in the same
vein; since you don't, I know emails from me won't change that.

-- 
Bryan Henderson                                    Phone 408-621-2000
San Jose, California

  parent reply	other threads:[~2006-12-22  7:11 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <787b0d920612192242x3788f4bfh3be846d4188e3767@mail.gmail.com>
2006-12-20  8:57 ` kill (was: Re: util-linux: orphan) Karel Zak
2006-12-20 10:03   ` kill Pádraig Brady
2006-12-20 10:45     ` kill Karel Zak
2006-12-20 21:45       ` kill Alfred M. Szmidt
2006-12-20 23:55         ` kill Karel Zak
2006-12-21  4:10           ` kill Evan Hunt
2006-12-21 16:34             ` splitting util-linux (was: kill) Bryan Henderson
2006-12-21 21:53               ` Karel Zak
2006-12-22  6:12                 ` Albert Cahalan
2006-12-22  7:13                   ` Bryan Henderson
2006-12-22  9:06                     ` Albert Cahalan
2006-12-22  7:23                   ` Bryan Henderson
2006-12-22  7:45                   ` Evan Hunt
2006-12-22  8:07                     ` Karel Zak
2006-12-22  8:45                       ` Evan Hunt
2006-12-22 11:03                         ` Karel Zak
2006-12-22 16:52                           ` Evan Hunt
2006-12-22 12:32                       ` Ian Kent
2006-12-22 10:24                   ` Karel Zak
2006-12-22 14:50                     ` Mark Rosenstand
2006-12-22 17:38                     ` Albert Cahalan
2006-12-25 20:03                     ` Albert Cahalan
2006-12-25 22:50                       ` Bryan Henderson
2006-12-22  6:44                 ` Bryan Henderson [this message]
2006-12-22  7:52                   ` Karel Zak
2006-12-21 10:51           ` kill Alfred M. Szmidt
2006-12-21 11:39             ` kill Martin Mares
2006-12-21 15:30               ` kill Karel Zak
2006-12-21 16:50               ` kill Alfred M. Szmidt
2006-12-21 17:38                 ` kill Albert Cahalan
2006-12-22  1:37                 ` kill Ian Kent
2006-12-20 15:00     ` kill Ian Kent
2006-12-20 16:58     ` kill Albert Cahalan
2006-12-20 16:33   ` kill (was: Re: util-linux: orphan) Albert Cahalan
2006-12-20 21:12     ` Karel Zak
2006-12-21  2:32       ` Albert Cahalan

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=42767.bryanh@giraffe-data.com \
    --to=bryanh@giraffe-data.com \
    --cc=P@draigbrady.com \
    --cc=acahalan@gmail.com \
    --cc=ams@gnu.org \
    --cc=ethanol@armory.com \
    --cc=kzak@redhat.com \
    --cc=util-linux-ng@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