Building Candlepin in Brew using Mead

Adam Young ayoung at redhat.com
Fri May 28 19:05:16 UTC 2010


On 05/28/2010 03:01 PM, Jesus Rodriguez wrote:
> On Fri, May 28, 2010 at 01:49:39PM -0400, Mike Bonnet wrote:
>    
>> On 05/28/2010 01:10 PM, Jesus M. Rodriguez wrote:
>>      
>>> On 05/13/2010 05:58 PM, Adam Young wrote:
>>>        
> [snip]
>
>    
>> The best write-up on MEAD at a high level is in a proposal to use it in
>> Fedora (note this hasn't really been discussed with a wide audience yet):
>>
>> http://fedoraproject.org/wiki/KojiMavenSupport
>>      
>
> Thanks for that information.
>
> [snip]
>
>    
>> The top-level entry-point to a MEAD build is a Maven pom.xml file.
>> buildr has a different entry point, so MEAD would need to be modified to
>> understand and use that.
>>
>> Note that buildr support is *way* down on my priority list, and I
>> haven't even discussed with the rest of RCM is buildr is a tool we
>> want/need to support directly in Brew/MEAD.  The better alternative in
>> my view is getting Candlepin to use Maven instead of buildr.
>>      
> I understand. I didn't know how far along MEAD has come. The original
> thought was to get all of the dependent rpms packaged, then use
> normal BuildRequires: in the spec file, and have buildr pull in the
> jars locally from /usr/share/java. We did something similar with Satellite
> using ant.
>
>    

I still think that is the best long term approach.  The Mead approach is 
more for getting a product available in a shorter time frame.  
Considering the large number of build deps that Candlepin has currently, 
getting them all into Fedora is a lot of work.  I'd not want to delay 
shipping Candlepin due to still hunting down those issues.  Thus the 
mead approach is, for Candlepin, a stopgap.  Perhaps making a skeleton 
Maven pom that works with mead but that doesn't have the full set of  
developers tool would be a short cut.







More information about the candlepin mailing list