public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
Search results ordered by [date|relevance]  view[summary|nested|Atom feed]
thread overview below | download: 
* Re: [gentoo-dev] metadata revised - removal of packages
  @ 2005-09-09 15:23 99%   ` Diego 'Flameeyes' Pettenò
  0 siblings, 0 replies; 1+ results
From: Diego 'Flameeyes' Pettenò @ 2005-09-09 15:23 UTC (permalink / raw
  To: gentoo-dev

[-- Attachment #1: Type: text/plain, Size: 1148 bytes --]

On Friday 09 September 2005 14:46, Mike Frysinger wrote:
> and then what ?  if you're proposing removal of packages due solely to no
> maintainer, then we're going to have to slap you around.  dont remove
> packages for that reason alone.
Exactly the point. And I follow this request. If that was the case, publib and 
libiconv would have been removed from the tree a lot of time ago, while they 
are now maintained by BSD herd and by me, as they are useful for portability.

Unfortunately, seems like Ciaran thinks that removing them is the only way to 
go, also if they can be perfect and just be unmaintained, because ebuilds 
risk to not pass future repoman tests and needs to be qa-checked from time to 
time, adding more work.

Well that's why we have a QA team, isn't it? For most of the changes in 
repoman check is possible to run a whole-tree check and then who propose the 
change can take care of fixing the unmaintained parts, like I did for 
enewuser/cp-a/chown root:root bugs.

-- 
Diego "Flameeyes" Pettenò
Gentoo Developer - http://dev.gentoo.org/~flameeyes/
(Gentoo/FreeBSD, Video, Gentoo/AMD64, Sound, PAM)

[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]

^ permalink raw reply	[relevance 99%]

Results 1-1 of 1 | reverse | options above
-- pct% links below jump to the message on this page, permalinks otherwise --
2005-09-09  9:58     [gentoo-dev] metadata revised - removal of packages Torsten Veller
2005-09-09 12:46     ` Mike Frysinger
2005-09-09 15:23 99%   ` Diego 'Flameeyes' Pettenò

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox