On Fri, 11 Dec 2009 15:44:12 +0100 Ulrich Mueller wrote: > >> I'm not looking to start a fight, and frankly after a year or so > >> I've learned to just subconsciously/automatically ignore kdebuild, > >> but why exactly must this be in pms? > > > Because we have not yet established that no users have kdebuild > > things installed. > > This is not a fact that could ever be verified, therefore your > argument is nonsensical. Yes it is. All you have to do is send an email to a mailing list that gets read by everyone who could be using kdebuild-1, and give them a reasonable time to reply. Alternatively, you could target a news item at those users, informing them of the removal. Either is entirely doable and a totally reasonable measure to take. > > Thus, package managers that support it have to go on supporting it. > > Once kdebuild can be safely removed from package managers that have > > supported it, it can then be removed from PMS. > > Last mention of kdebuild was removed from the KDE overlay at > 2008-09-23, which was more than one year ago. Generally we don't > support upgrades of outdated systems for more than one year. The genkdesvn overlay was around for considerably longer than that. Also, we're talking *installed* packages here, not installable ones. Users have installed packages going back a very very long time. > But it's irrelevant anyway, since it was never an approved EAPI. > Therefore, we can remove it any time. > > And as was already pointed out several times, there was a council > decision about the issue in the 2008-04-10 meeting: > > | The council voted that kdebuild-1 and other unapproved EAPIs could > | not be in an approved PMS document. The spec isn't a place for > | proposals or things that will never be submitted for approval by > the | council. It's a specification, a reference of what is allowed > in the | main tree. And there is a way of getting PMS built without kdebuild-1, for approval. In the mean time, PMS is there to be useful to package manager developers, and so kdebuild-1 needs to remain so long as package managers support it. -- Ciaran McCreesh