On 05/14/2010 08:30 AM, Bryan Kearney wrote:
On 05/13/2010 10:41 PM, Jesus M. Rodriguez wrote:
> On Thu, May 13, 2010 at 5:58 PM, Adam Young<ayoung(a)redhat.com> wrote:
>
>> Mike Bonnet was good enough to spend a couple of hours with me getting
>> me up to speed on what he is doing with Mead. The short of it is that
>> he has a middle grouind between mavne repository fetching and JPackage
>> for building Maven based projects.
>>
>> In order to take advantage of it, we have one of two choices.
>>
>> 1. Move Candlepin over to maven
>> 2. Help him get Mead able to use buildr.
>>
>> Note that this would produce a usable build without having to use all of
>> the MySpec RPMS I built. We could selectively use them if we desire.
>>
>> I like option 2, although I might not be able to see it through. In
>> order to do this, we have to close the loop on buildr doing local
>> repository builds. As I can see it this means modifying the -r
>> localbuild option such that, once the localbuild script has modified the
>> remote and local repository values, they can no longer be modified by
>> the buildfile. I think I can make this happen, I'll let you know. It
>> might take an additional patch to buildr.
>>
> I too like option 2 :) but I'm biased.
>
I am willing to go with option (2), but I look at this as somewhat of a
rathole. If it starts to get nasty, I will be inclined to push to go to
maven even though everyone will hate me for it.
We discussed it, and the amount of work didn't seem too daunting.
Mostly it was providing a different setup up, but the rest of the rules
for a maven build still hold true for a buildr build.
>
>> We also need to hack the emma code inside of buildr to not try and
>> download emma from a remote repository.
>>
>> Once that is done, Mike needs to provide an extension to the command
>> line interface to brew: something like brew-buildr, and then modify how
>> that calls brew such that it knows to do a buildr -r localbuild type
>> build. The localbuild file will be something that he controls as part
>> of the mead/brew system, and that will manage the repos used to build
>> candlepin.
>>
> This is great for an officially supported release, but what about a community
> release? usually that has to occur from koji or something like that.
>
good question. Are there plans for MEAD getting into the Fedora env?
This is a question above my paygrade, but my gut says that Mead is more
a Red Hat solution for dealing with JBoss, and that the Fedora approach
is going to continue to be JPackage based.
-- bk
_______________________________________________
candlepin mailing list
candlepin(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/candlepin