DragonFly BSD
DragonFly users List (threaded) for 2005-08
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: Compatability with FreeBSD Ports

From: Chris Pressey <cpressey@xxxxxxxxxxxxxxx>
Date: Fri, 12 Aug 2005 19:49:46 -0700

On Sat, 13 Aug 2005 00:36:42 +0100
Hiten Pandya <hmp@xxxxxxxxxxxxx> wrote:

> Joerg Sonnenberger wrote:
> > On Fri, Aug 12, 2005 at 12:37:11PM -0500, ejc wrote:
> > You can still expect a bunch of problems with KDE, they are still
> > not all fixed.
> > 
> > Joerg
> That just brought another thought of mine to foreground, given the 
> development style of DragonFly; just as we give utmost priority to fix
> bugs in the core system, I thinkw we should also prepare a list that 
> contains a list of packages that are necessary from a general user's 
> perspective.
> We have to put personal differences aside, i.e., "I am only going to
> fix  Gnome because that's what I use," is kind of attitude which is
> absolutely  not called for.
> To summarise, we need to compile a list of pkgsrc packages that are
> used  most by DragonFly users.

Allow me to submit a rebuttal (don't take this too seriously ;) speaking
from a theory of open-source as a self-organizing system of individuals
working strictly on their own time and strictly for their own interests:

Why should I fix Gnome if I don't use it?

Why should I scratch an itch that I don't have?

If lots of users use Foo, then lots of patches to get Foo working will
come in, and Foo will be well-maintained.  If no users use Bar, then no
patches for Bar will come in, and Bar will rot.  Problem solved - the
packages that are well-maintained are exactly the ones that are in
demand.  What need is there for a list?  How is it not just another,
unnecessary level of organization on top of something that already
organizes itself automatically?

Just something to think about...


[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]