<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 09/10/13 08:48, Jeroen van Meeuwen
wrote:<br>
</div>
<blockquote cite="mid:4526907.c1Df9kiW4a@albert.kolabsys.com"
type="cite">
<pre wrap="">On Wednesday, October 09, 2013 02:40:01 AM Tormen wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 08/10/13 20:37, Jeroen van Meeuwen wrote:
</pre>
<blockquote type="cite">
<pre wrap="">I've just successfully completed an "aptitude install kolab" on a
fresh Debian Wheezy system, configured to include "Kolab:3.1" and
"Kolab:3.1:Updates".
</pre>
</blockquote>
<pre wrap="">
I did NOT try with /updates/ (but only with Kolab:3.1) !
... because for me /updates/ are something additional / optional that
comes after a base install ^^
</pre>
</blockquote>
<pre wrap="">
Updates are good though, this is where future fixes will end up.
For some additional speed as to what might get updated,
Kolab:Development should <b class="moz-txt-star"><span class="moz-txt-tag">*</span>always<span class="moz-txt-tag">*</span></b> have the latest versions of things
(but is unstable in that regard).
</pre>
</blockquote>
<br>
Hmm. Your answer gives me the impression that you did not understand
my point yet<br>
(very probably because of my poor english and/or because I am too
sleep deprived!!).<br>
<br>
So I will try to be more clear :)<br>
<br>
Take for instance DEBIAN:<br>
To install a base debian system, you need this one line:<br>
<br>
deb <a class="moz-txt-link-freetext" href="http://ftp.fr.debian.org/debian/">http://ftp.fr.debian.org/debian/</a> wheezy main<br>
<br>
And this package repo is /self-contained/ and suffices to install a
running Debian.<br>
Any unfulfilled packaged dependency within this Debian repository
would be a /bug/.<br>
<br>
So to simply install a base system you do NOT need any sort of
update sources like:<br>
deb <a class="moz-txt-link-freetext" href="http://security.debian.org/">http://security.debian.org/</a> wheezy/updates main<br>
# where the security will come from... once my debian is
installed, but not to install it ^^<br>
<br>
deb <a class="moz-txt-link-freetext" href="http://ftp.debian.org/debian">http://ftp.debian.org/debian</a> wheezy-backports main<br>
# where some day-to-day software will come in its latest version
and glory (like libreoffice for instance), but again nothing you
/need/ to have in your sources.list in order to install debian.<br>
<br>
<br>
<blockquote cite="mid:4526907.c1Df9kiW4a@albert.kolabsys.com"
type="cite">
<pre wrap="">For some additional speed as to what might get updated,
Kolab:Development should *always* have the latest versions of things
(but is unstable in that regard).</pre>
</blockquote>
<br>
I still think that any inter-package repository dependency (from a
base repo into an update repo) is a bug.<br>
<br>
[1] deb <a class="moz-txt-link-freetext" href="http://obs.kolabsys.com:82/Kolab:/3.1/Debian_7.0/">http://obs.kolabsys.com:82/Kolab:/3.1/Debian_7.0/</a> /<br>
[2] deb
<a class="moz-txt-link-freetext" href="http://obs.kolabsys.com:82/Kolab:/3.1:/Updates/Debian_7.0/">http://obs.kolabsys.com:82/Kolab:/3.1:/Updates/Debian_7.0/</a> /<br>
<br>
[2] can depend on things from [1] ... if to fix a bug or get new
functionality there is a new dependency that has arise...<br>
[1] should on the other hand not depend on [2], or else:<br>
This is not at all intuitive and conform how to how it usually
works.<br>
Which is why I am writing you this to see if this is really the
dependency setup that you wanted.<br>
<br>
<br>
Best,<br>
<br>
Tormen.<br>
<br>
</body>
</html>