Mailinglist Archive: opensuse-buildservice (251 mails)
| < Previous | Next > |
Re: [opensuse-buildservice] How can I configure download on demand to use an RPM repository?
- From: Marcus Hüwe <suse-tux@xxxxxx>
- Date: Wed, 29 Sep 2010 11:42:56 +0200
- Message-id: <20100929094256.GA4209@linux>
On 2010-09-28 11:31:38 -0500, Michael E Brown wrote:
correctly the obs should fetch the required metadata on its own?
In order to support non static metadata (without "hacks" like
removing :full* and triggering a scanrepo event) we would just
need to compare the old metadata with the new metadata and remove
some entries from :full.solv (and their correspondent binaries from
the :full/ dir). I think this shouldn't be too hard to implement:)
Marcus
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
On Tue, Sep 28, 2010 at 11:14:12AM -0500, Robert Xu wrote:Can you summarize which features do you miss? If I understand you
On Tue, Sep 28, 2010 at 06:24, Marcus Hüwe <suse-tux@xxxxxx> wrote:
On 2010-09-28 12:03:58 +0200, Francisco Javier Cuadrado wrote:
Afterwards restart the scheduler.
This got my attention...
So would this let us get RPMs that are continually updated, like from
a repo such as Fedora Updates?
Absolutely not. In fact, this seriously breaks and wont work at all due to
some
limitations of DoD. The repo you pull from has to be completely static. The
build service never re-downloads the repo metadata, and caches a lot of info.
correctly the obs should fetch the required metadata on its own?
In order to support non static metadata (without "hacks" like
removing :full* and triggering a scanrepo event) we would just
need to compare the old metadata with the new metadata and remove
some entries from :full.solv (and their correspondent binaries from
the :full/ dir). I think this shouldn't be too hard to implement:)
Marcus
--
To unsubscribe, e-mail: opensuse-buildservice+unsubscribe@xxxxxxxxxxxx
For additional commands, e-mail: opensuse-buildservice+help@xxxxxxxxxxxx
| < Previous | Next > |