Re: CDD-package inside of Debian or out?
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On 25-05-2005 14:26, Andreas Tille wrote:
> On Wed, 25 May 2005, Jonas Smedegaard wrote:
>
>> 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.
>
> Sure.
Great :-D
>> The point of this whole thread is wether or not it makes sense to always
>> assume a CDD wants to be within Debian.
>
> Well, at least we agreed to this definition. If we *define* CDD is
> completely inside Debian than something outside Debian can not be a
> CDD. I would not say that something outside Debian which is using
> CDD techniques are not allowed to exist.
Sorry - sorry. I didn't mean to start over that flawed discussion again :-)
Replace "within Debian" above with "within standard Debian distribution".
"Debian sarge" is a "standard Debian distribution" (a non-custom one).
"Debian etch" is another "standard Debian distribution".
"Skolelinux/sarge" will probably be a "Debian-derived distribution".
"Skolelinux/etch" will hopefully be "completely within Debian", but hos
to release it? As a "custom Debian distribution" on a single CD? As a
"Skolelinux flavor" of install methods? Not released by itself at all
(officially by Debian)?
It seems cddtk aims at generating "smart metapackages" to be included in
the common Debian distribution.
One of the aims of Skolelinux is to fit on a single CD. Do we need
another tool for that or is cddtk the tool also for such "outer" factors
as distribution media limitations?
>> 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).
>
> Ohh no, not again. ;-))
>
> I usually add packages from the non-free part as "Suggests:" to my
> meta packages. So as long as GFDL would stay in non-free I will
> not have to change anything.
...and when they are just suggested, you need to manually and explicitly
pull them in. WHAM! there goes your automated distro build tool :-(
I want automation, also for customizations outside of the Debian
distribution (but possibly not outside of whole Debian - note the
difference!).
I want my CDD "source" to generate dependencies depending on the sources
available, not hardcoded dependencies! If With non-US and non-free
sources are added (which they are not for the official "compile" of the
CDD package for Debian) then I want it to take those archives into
consideration when generating the package.
...or the skolelinux.no or Ubuntu pool of packages.
I want a tool not hardcoded to a specific package pool (typically being
that of the most recently released official common Debian distribution).
Instead I want a tool dealing flexibly with packages available.
That's why I see a point in using debtags instead of hardcoding.
:-)
- 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
iD8DBQFClH6bn7DbMsAkQLgRAsNFAJwPqWIvcx6Frl4GtAVr4zbXdw9oVQCgghg2
06cuFywJF+KAOVFv5e9mkhE=
=VtCp
-----END PGP SIGNATURE-----
Reply to: