From: Maciej Mrozowski <reavertm@gmail.com>
To: gentoo-pms@lists.gentoo.org
Subject: Re: [gentoo-pms] kdebuild-1 conditionales
Date: Fri, 11 Dec 2009 11:45:53 +0100 [thread overview]
Message-ID: <200912111145.54390.reavertm@gmail.com> (raw)
In-Reply-To: <20091211081754.GA6529@hrair>
[-- Attachment #1: Type: Text/Plain, Size: 3243 bytes --]
On Friday 11 of December 2009 09:17:54 Brian Harring wrote:
> On Thu, Dec 10, 2009 at 10:27:30PM +0000, Ciaran McCreesh wrote:
> > * Don't mess with kdebuild until you're sure that no-one has any
> > kdebuild packages installed.
>
> 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?
>
> It's experimental w/ low user acceptance, and was fundamentally
> outside the gentoo mainstream. If long term maintenance of it is
> desired for anyone who hasn't yet punted those ebuilds from their
> vdb, maintain it in a branch rather then the effective head (don't
> make the mainline suffer maintenance for something that was outside
> mainline).
>
> My two cents mind you- at this point, flipping through the source, the
> kdebuild bits disrupt the flow from my view (and more importantly the
> resultant read of it due to folks trying to structure the text to be
> agnostic to non-kdebuild), more importantly doing so w/ minimal gain
> for the mainstream.
>
> Either way, take it as a +1 for punting it from mainstream and making
> the kdebuild specific folk maintain their own branch rather then
> general eapi (gentoo specific) having to maintain it. Branching of
> this sort is presumably one of the reasons pms uses a dvcs after all.
>
> And to head off one angle of argument, I fully expect if I ever get
> ambitious enough to derive an eapi extension that I'll have to
> maintain it outside of pms mainline- being nonstandard, I'd expect
> nothing less (hence the +1 for punting kdebuild).
>
> My two cents either way, and well aware it's probably not something
> everyone wants to hear.
>
> Not a hard +1 since I've zero interest in a fight also, but a +1
> either way.
>
> Sorry, but tis my views.
> ~harring
PMS document is meant to provide information that can be relied upon.
kdebuild-1 was used only during short period of time two years ago and only
supported by one package manager. Gentoo KDE team has already expressed no
interest in kdebuild-1 long time ago as well[1].
That being said kdebuild-1 can no longer be relied upon as a effective
specification - it does not have implementation in official package manager
and no new kdebuild-1 is going to be created ever by any Gentoo project - it's
effectively dead besides all known .
Also, what's the most important - any official packages in kdebuild-1 format
has already been replaced (with no loss of functionality, we're talking about
KDE 4 ebuilds here) by official packages in EAPI-2 format - format supported
by three most popular package managers and users as advised to migrate (if
they haven't already) to those packages.
Otherwise they're unsupported anyway - and PMS needs to document things that
are supported and can be relied upon.
There's anything more to add - kdebuild-1 PMS specification should be
maintained by those interested in separate git branch, and completely removed
from PMS trunk as it only serves as LaTeX code obfuscator.
http://www.mail-archive.com/gentoo-dev@lists.gentoo.org/msg33146.html
On behalf of Gentoo KDE
--
regards
MM
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-12-11 12:15 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-10 20:48 [gentoo-pms] kdebuild-1 conditionales Christian Faulhammer
2009-12-10 22:27 ` Ciaran McCreesh
2009-12-11 6:08 ` Ulrich Mueller
2009-12-11 13:56 ` Ciaran McCreesh
2009-12-11 15:02 ` Ulrich Mueller
2009-12-11 17:06 ` Ciaran McCreesh
2009-12-11 17:26 ` Ulrich Mueller
2009-12-13 14:13 ` Ciaran McCreesh
2009-12-11 15:03 ` David Leverton
2009-12-11 8:17 ` Brian Harring
2009-12-11 10:45 ` Maciej Mrozowski [this message]
2009-12-11 13:59 ` Ciaran McCreesh
2009-12-11 14:23 ` Christian Faulhammer
2009-12-11 17:07 ` Ciaran McCreesh
2009-12-11 13:57 ` Ciaran McCreesh
2009-12-11 14:44 ` Ulrich Mueller
2009-12-11 17:02 ` Ciaran McCreesh
2009-12-11 17:11 ` Ulrich Mueller
2009-12-11 17:18 ` Ciaran McCreesh
2009-12-11 17:34 ` Ulrich Mueller
2009-12-11 17:43 ` Ciaran McCreesh
2009-12-11 18:14 ` Ulrich Mueller
2009-12-11 18:27 ` Ciaran McCreesh
2009-12-11 19:42 ` Brian Harring
2009-12-11 19:53 ` Ciaran McCreesh
2009-12-11 20:30 ` Brian Harring
2009-12-11 20:54 ` Ciaran McCreesh
[not found] ` <200912122245.50521.vapier@gentoo.org>
2009-12-13 19:30 ` [gentoo-council] " Ciaran McCreesh
[not found] ` <200912132131.13308.vapier@gentoo.org>
2009-12-14 15:14 ` Ciaran McCreesh
[not found] ` <200912141201.04887.vapier@gentoo.org>
2009-12-14 18:21 ` Ciaran McCreesh
2009-12-14 20:58 ` Brian Harring
[not found] ` <1260817256.7072.7.camel@hangover>
2009-12-14 19:24 ` Ciaran McCreesh
2009-12-16 22:50 ` Christian Faulhammer
2009-12-16 23:08 ` Ciaran McCreesh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200912111145.54390.reavertm@gmail.com \
--to=reavertm@gmail.com \
--cc=gentoo-pms@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox