Mailinglist Archive: opensuse-factory (673 mails)
| < Previous | Next > |
Re: [opensuse-factory] Status openSUSE distribution
- From: Adrian Schröter <adrian@xxxxxxx>
- Date: Wed, 24 Sep 2008 10:01:30 +0200
- Message-id: <200809241001.30792.adrian@xxxxxxx>
On Wednesday 24 September 2008 08:27:36 wrote Hans Petter Jansson:
It is not guaranteed, but it can checked before. This is what we need to make
easier for our Rudi's.
It is also not guaranteed that it breaks other packages, but this is what we
test in our Beta distribution internally or in home:rguenther:playground on
risky packages.
There is a bit in the wiki, but we work currently on automatization of this
and integrating into osc for local builds. So it will become lots easier
soon.
bye
adrian
--
Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
email: adrian@xxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
On Wed, 2008-09-24 at 09:19 +0200, Adrian Schröter wrote:
On Wednesday 24 September 2008 07:54:28 wrote Hans Petter Jansson:
On Wed, 2008-09-24 at 07:49 +0200, Adrian Schröter wrote:
This makes me wonder if we couldn't establish a repo on top of the
"breakable" one, which would automatically pull in packages that build
successfully and don't cause any dependency problems (pulling sets of
packages together when necessary to maintain dependencies). That repo
will then always be consistent with itself, although it may contain
older packages in some cases.
These are our devel projects, each package has one. For example changes
on the KDE stack are taken from KDE:KDE4:Factory:Desktop.
Ok - so when a package is pushed from the devel project to
openSUSE:Factory, it is guaranteed to build and not have broken
dependencies in the context of openSUSE:Factory? Is there an automatic
check for this?
It is not guaranteed, but it can checked before. This is what we need to make
easier for our Rudi's.
It is also not guaranteed that it breaks other packages, but this is what we
test in our Beta distribution internally or in home:rguenther:playground on
risky packages.
We could then generate installation media from that repo - and since
many types of problems are already fixed (everything builds, all
dependencies are satisfied, there are no file conflicts), we could do
so more frequently.
You can do so, just apply the devel projects in addition to that in the
product definition/kiwi. However, I can promise you, when apply all, you
will never have a working system ;)
I feel like we're talking past each other here :) If openSUSE:Factory is
guaranteed to always be building and have working dependencies, and
devel projects aren't, I'd draw the packages from openSUSE:Factory,
obviously.
By the way, is there a good, up-to-date wiki page on how the ISOs are
made, from start to finish?
There is a bit in the wiki, but we work currently on automatization of this
and integrating into osc for local builds. So it will become lots easier
soon.
bye
adrian
--
Adrian Schroeter
SUSE LINUX Products GmbH, GF: Markus Rex, HRB 16746 (AG Nürnberg)
email: adrian@xxxxxxx
---------------------------------------------------------------------
To unsubscribe, e-mail: opensuse-factory+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-factory+help@xxxxxxxxxxxx
| < Previous | Next > |