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

Re: CDD-package inside of Debian or out?



-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 24-05-2005 19:03, Andreas Tille wrote:
> On Tue, 24 May 2005, cobaco (aka Bart Cornelis) wrote:
> 
>> I can easily see a KDE-CDD being created with the aim of creating one or
>> more good default setups aimed at different use-cases (developer,
>> office-worker, home-user, ...)
> 
> Sure.  But I know by own experience that running a CDD has to be *done*
> by *somebody*.  I see no driving force behind this kind of CDD and thus
> I do not see this happen.  If I should be wrong - it's fine for me.

The above was spawned from the below:


On 23-05-2005 14:36, Jonas Smedegaard wrote:
> On 21-05-2005 18:20, Andreas Tille wrote:

>>>If you ask me a CDD should not really depend from a certain desktop
>>>environment but on certain applications which are needed by the end
>>>users.
>
>
> What choices a CDD should or should not remove from the local admin
> is IMHO not for us to define as developers of a _common_ framework
> for CDDs.


So you do agree with me after all, Andreas, that if someone choose to
put the "driving force" behind a CDD based on a desktop (suite:: facet)
instead of a set of needed applications (use:: facet), then we welcome that.

In other words, we should make our cdd toolkit generic, not tied to
specific facets!


What difference it makes? Well, some facets (like use::) go well
together, byt others (like suite::) may conflict with each other.


The point of this whole thread is wether or not it makes sense to always
assume a CDD wants to be within Debian. A CDD for "Cool multimedia" may
choose to include patent-risky compilation options to ffmpeg and
mplayer. A "Best of GNU" CDD may want the GNUstep desktop (without
non-GNU software "polluting" the menus!) and GFDL documentation (which
is considered non-free by Debian).


Both of the above CDDs have a large community behind them (just check
out the discussions in -devel about mplayer in Debian). The first one
would "only" need an autobuilder applying compile options based on
tagging (yes, same tags used for package selection and for
picking/adapting config tweaks!). The other would "only" need a
"licensing::" facet added to debtags and -doc packages tagged as they
flood non-free when sarge gets released and the GFDL-vote kicks in.


 - Jonas

- --
* Jonas Smedegaard - idealist og Internet-arkitekt
* Tlf.: +45 40843136  Website: http://dr.jones.dk/

 - Enden er nær: http://www.shibumi.org/eoti.htm
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFClFWon7DbMsAkQLgRApByAKCYooWk4InLgftYAu/yZycz/TYj9QCePAA0
vENL3hLBXo2OedhePLZPERE=
=dKsI
-----END PGP SIGNATURE-----



Reply to: