[prev in list] [next in list] [prev in thread] [next in thread]
List: gentoo-desktop
Subject: [gentoo-desktop] Fwd: what packages do we want distros to ship ?
From: "Theo Chatzimichos" <tampakrap () gmail ! com>
Date: 2008-12-22 9:28:53
Message-ID: 26638a180812220128j766f580bm74abbfc2e8080c4d () mail ! gmail ! com
[Download RAW message or body]
I think we should prepare an official answer here as Gentoo KDE Team so
state your opinions. I'll reply later as i am busy right now
---------- Forwarded message ----------
From: Alexander Neundorf <neundorf@kde.org>
Date: Mon, Dec 22, 2008 at 10:46 AM
Subject: what packages do we want distros to ship ?
To: kde-core-devel@kde.org
Cc: release-team@kde.org
Hi,
since I'm doing the build stuff I'm getting in contact with packagers from
distributions and their wishes.
One thing which I don't know what the current state is, is what type of KDE
packages do we want distributions to ship ?
We have the "modules" kdelibs, kdebase, kdepim etc. These are quite
corse-grained.
E.g. Slackware ships them that way, so you get a package kdebase.tar.gz
etc.#
E.g. Gentoo is on the other end, they modify the buildsystem so that they
can
ship everything as a single package. E.g they'd like to have a separate
package for each library in kdebase/workspace/.
Now, we could say, it's up to them, we don't care.
But that wouldn't be good. It would be better if we support what we want
them
to ship, so they have to do less (or no) modifications and we know what will
be shipped to our users.
Also making more fine-grained packages than whole-module-one-package can be
made easier for them if we consider this when writing the CMakeLists.txt.
(e.g. by keeping in mind that CMAKE_SOURCE_DIR and CMAKE_BINARY_DIR are
different when building a whole module instead of independent, by making
configure tests local to the application, etc.).
So, what do we expect what will be shipped ?
My guess is that it's somewhere in between, e.g. whole kdelibs, whole
kdepimlibs, whole kdebase/workspace libs, but separate e.g. kontact, kate,
kwin, kmail etc.
Alex
[Attachment #3 (text/html)]
I think we should prepare an official answer here as Gentoo KDE Team so state your \
opinions. I'll reply later as i am busy right now<br><br><div \
class="gmail_quote">---------- Forwarded message ----------<br>From: <b \
class="gmail_sendername">Alexander Neundorf</b> <span dir="ltr"><<a \
href="mailto:neundorf@kde.org">neundorf@kde.org</a>></span><br>
Date: Mon, Dec 22, 2008 at 10:46 AM<br>Subject: what packages do we want distros to \
ship ?<br>To: <a href="mailto:kde-core-devel@kde.org">kde-core-devel@kde.org</a><br>Cc: \
<a href="mailto:release-team@kde.org">release-team@kde.org</a><br> <br><br>Hi,<br>
<br>
since I'm doing the build stuff I'm getting in contact with packagers \
from<br> distributions and their wishes.<br>
One thing which I don't know what the current state is, is what type of KDE<br>
packages do we want distributions to ship ?<br>
We have the "modules" kdelibs, kdebase, kdepim etc. These are quite<br>
corse-grained.<br>
E.g. Slackware ships them that way, so you get a package kdebase.tar.gz \
etc.#<br> <br>
E.g. Gentoo is on the other end, they modify the buildsystem so that they can<br>
ship everything as a single package. E.g they'd like to have a separate<br>
package for each library in kdebase/workspace/.<br>
<br>
Now, we could say, it's up to them, we don't care.<br>
But that wouldn't be good. It would be better if we support what we want them<br>
to ship, so they have to do less (or no) modifications and we know what will<br>
be shipped to our users.<br>
Also making more fine-grained packages than whole-module-one-package can be<br>
made easier for them if we consider this when writing the CMakeLists.txt.<br>
(e.g. by keeping in mind that CMAKE_SOURCE_DIR and CMAKE_BINARY_DIR are<br>
different when building a whole module instead of independent, by making<br>
configure tests local to the application, etc.).<br>
<br>
So, what do we expect what will be shipped ?<br>
<br>
My guess is that it's somewhere in between, e.g. whole kdelibs, whole<br>
kdepimlibs, whole kdebase/workspace libs, but separate e.g. kontact, kate,<br>
kwin, kmail etc.<br>
<br>
Alex<br>
</div><br>
[prev in list] [next in list] [prev in thread] [next in thread]
Configure |
About |
News |
Add a list |
Sponsored by KoreLogic