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

Re: Preparing a Proposal: 3 DD needed for every NEW package

On Sat, Dec 29, 2001 at 02:14:15PM +0100, Josselin Mouette wrote:
> Lenart Janos a icrit :
> > 
> > As you might already have noticed Debian begun to bloat - so many
> > unneeded, unused, unmaintained(!) packages.
> I don't think all these packages should be swept out. Unmaintained 
> packages that don't have bunches of bugs shouldn't be a problem, for 
> example.
> A better solution, IMO, would be to evaluate which packages should be 
> removed from the archive (and I believe there are not very much). To do 
> that, one could consider the orphaned packages that have important bugs, 
> ore more than N (define N as you like) normal bugs. A large part of them 
> could certainly be replaced by other (maintained) ones. Then, a 
> Replaces: field should be added in those packages - or maybe replaces is 
> too strong and we would have to add another field.
> For the other ones (unmaintained, buggy, AND without replacement), the
> users should be clearly informed when installing the, and maybe the
> package could be removed from the archive after 2 releases.

Add also that packages can reach their End-Of-Life time. 
So, no more upstream maintainer(s), no more active development and more valid
alternatives to them. This is unfortunately true for so much pkgs.
Currently I do not see any valid management of this kind of problem in the 
Project, but for maintainer minds. 
Apparently, too much maintainers are not really active
and too much pkgs are built up without a RFP. Some packages are
built starting from beta-quality sw, and this is not a good practice.
Burocracy cannot solve these problems. Maintainers intelligence could.

Francesco P. Lovergine

Reply to: