[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [p2-dev] ECF p2 repos are missing
- From: Paul Webster <pwebster@xxxxxxxxxxxxxxxxxxx>
- Date: Wed, 27 Oct 2010 07:58:31 -0400
- Delivered-to: email@example.com
- Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=kYOqLHAtURRdmCO5syTyqrpSonGg+75wVfPv2Ax1xeaqY2d+MmKQt1RZv8yuHluGHf E5L/Axohp0eWFuKMWu7PrpUNCW8y8vRU3TqqYFWjuJ5H2M3SU4Ok1af5lx18dMzuxNO2 US/xUwmTiQ2G2w5VboPmF8x4UkPsDK+XRypSw=
On Tue, Oct 26, 2010 at 11:23 PM, Scott Lewis <slewis@xxxxxxxxxxxxx>
We would like to move to a model where we build all our bundles with our builder, produce a p2 repo, and the ECF filetransfer bundles are consumed by the platform from that repo. ÂThat seems doable to me...as it should be possible for the platform releng to simply read/retrieve the relevant (filetransfer) bundles from out of the repo created by our builder....rather than what we are doing now with map file entries...which is clumsy, error prone all around, and costly for us.
If the platform switches to p2IU map file entries, then they would be able to get either specific versions from a repo, or the latest from the repo ... the URL would still need to be stable, but doesn't have to be as specific (with composite repos) as the curret HTTP GET.Â ex:
You could even provide a composite repo specifically for platform consumption.Â Promoting a build for the platform to use would just mean mirroring it in.
Hi floor.Â Make me a sammich! - GIR