| Buckminster Aggregator Target Configurations [message #524580] |
Thu, 01 April 2010 13:52  |
 Johannes Tysiak
Messages: 4
Registered: April 2010 |
Junior Member |
|
|
Hi,
I am currently trying to create several target platforms using Buckminster. To save some bandwidth, I decided to set up a local mirror of the relevant update sites I need for these target platforms, in order to make the creation process more efficient. I am trying to use the Buckminster Aggregator feature to create the aggregated mirror.
So far so good.
My problem is that using the Buckminster Aggregator only allows to aggregate for the "common" configurations (win32, linux, macosx), while there is no way to create configurations for other systems (such as solaris).
I personally would not need any configurations besides the "common" ones mentioned above. However, when I try to materialize a p2 target platform using Buckminster, I can only use wildcards as target settings as opposed to a list of valid configurations. Because of this, Bucky also tries to materialize the platform for all "exotic" configurations. Of course it fails, as there are no platform specific fragments on my aggregated mirror for these "exotic" configs.
I tried out both the Buckminster Aggregator as well as the B3 Aggregator, as I read that the Helios release site is built using the aggregation feature. I already found the *.build files for the Helios release site, however I cannot figure out how "exotic" configs come into play here.
Can anyone give me a hint, please?
Cheers,
Joe
|
|
|
| Re: Buckminster Aggregator Target Configurations [message #524586 is a reply to message #524580] |
Thu, 01 April 2010 14:08  |
|
Hi Johannes,
This sounds like an unnecessary limitation. Can you please file a bugzilla? Use Modeling / EMFT.b3.
Thanks,
Thomas Hallgren
On 04/01/2010 03:52 PM, Johannes Tysiak wrote:
> Hi,
>
> I am currently trying to create several target platforms using
> Buckminster. To save some bandwidth, I decided to set up a local mirror
> of the relevant update sites I need for these target platforms, in order
> to make the creation process more efficient. I am trying to use the
> Buckminster Aggregator feature to create the aggregated mirror.
>
> So far so good.
>
> My problem is that using the Buckminster Aggregator only allows to
> aggregate for the "common" configurations (win32, linux, macosx), while
> there is no way to create configurations for other systems (such as
> solaris).
>
> I personally would not need any configurations besides the "common" ones
> mentioned above. However, when I try to materialize a p2 target platform
> using Buckminster, I can only use wildcards as target settings as
> opposed to a list of valid configurations. Because of this, Bucky also
> tries to materialize the platform for all "exotic" configurations. Of
> course it fails, as there are no platform specific fragments on my
> aggregated mirror for these "exotic" configs.
>
> I tried out both the Buckminster Aggregator as well as the B3
> Aggregator, as I read that the Helios release site is built using the
> aggregation feature. I already found the *.build files for the Helios
> release site, however I cannot figure out how "exotic" configs come into
> play here.
>
> Can anyone give me a hint, please?
>
> Cheers,
> Joe
|
|
|
|
Powered by
FUDForum. Page generated in 0.02948 seconds
] 
Search
Help
Register
Login
Home
