On Sun, 20 Sep 2009 02:37:16 +0200
Patrick Lauer <firstname.lastname@example.org> wrote:
> > The KDE team are more than welcome to re-add it as an EAPI
> > controlled feature, either through EAPI 4 or through EAPI
> > kdebuild-2 as they prefer.
> > There's a huge difference between doing something as a published
> > standard and doing something that violates a published standard.
> Now you're being quite inconsistent. If you are in support of what
> the "old" KDE team / genkdesvn did (create their own standard in an
> overlay and experiment with it) then you must also be in support of
> the "new" kde team doing the same.
If they do it as a published standard, yes, I'm entirely in favour of
it and would be happy to provide any assistance they require. If they do
it without proper EAPI markings and as an undocumented extension, then
no, I don't approve.
> So either kdebuild-1 was a bad thing (not approved by council, not
> even supported by any official package manager) or package.mask as a
> directory is a good thing (feature has been there since the Old
> Times, only used in an overlay, well documented, no compatibility
package.mask as a directory as an extension that breaks
specification-compliant package managers is bad. As a documented,
standardised extension, it is good.
> Also, kdebuild-1 was used _before_ it was voted on by council (which
> doesn't seem to bother you because it was in an overlay) and never
> became an official standard (published yes, but that's irrelevant).
> So by your own logic using it was A Bad Thing To Do.
Published is entirely relevant. That it was approved by the KDE team
rather than the Council is not relevant, since it has no impact upon
anyone implementing a package manager.
> Or you only attacked funtoo (and their use of package.mask) for
> personal reasons?
I offered to help Funtoo do an EAPI funtoo-2 so they could use
package.mask as a directory. That offer remains open.
> I find this interpretation quite interesting, but I'm not that much
> into postmodern existentialism. You should do a subjective
> interpretation based on dadaism or the school of dancing goats.
> That being said I was merely pointing out that the statement in PMS
> ("bash version 3.0") has no base in reality anymore and has been de
> facto obsoleted. De jure the council has not voted against these
> violations, even when they were brought up quite a while ago
> (darkside claims 6-8 months ago).
They also haven't given us permission to change PMS.
> So independent of what you believe in or desire the statement in PMS
> is WRONG. As such it needs to be corrected.
PMS accurately reflects the most recent official decision from the
> If that happens on the short path by editing it directly or through
> the long path of letting council decide to have it edited doesn't
> matter to me, as long as PMS and reality can agree on basic things.
Then why have you still not followed the process to get the change
made? Why did you instead start blaming the PMS team for refusing to
exceed its authority?
> > > I would say that documenting the current state of things is quite
> > > relevant to the issue at hand. If you are bothered by facts please
> > > don't try to engage in discussions.
> > Then why don't you follow the process we told you about for getting
> > it fixed?
> Well, it's on the council's agenda now. I would say that it's
> following process quite well. How about you don't ask questions you
> already know the answer to?
I've still not seen a thread discussing it on gentoo-dev@. Is there a
particular reason you're bypassing the normal process?