On Thu, Aug 28, 2014 at 05:17:53PM +0200, Thomas Moschny wrote:
2014-08-28 14:05 GMT+02:00 Dan Horák <dan(a)danny.cz>:
> On Thu, 28 Aug 2014 13:55:14 +0200
> Miroslav Suchý <msuchy(a)redhat.com> wrote:
>
>> On 08/27/2014 08:17 PM, Darryl L. Pierce wrote:
>> > How do you build a package in koji when the package requires itself
>> > to be available?
>>
>> I seen a lot of packages where it was needed for %check section.
>> If this is the situation (you have to investigate that). Just comment
>> out that BR and %check section. Build it. Then uncomment and build
>> again. Of course if you can put there %boostrap macro, you will easy
>> work for others.
>
> And you might try building an older version that didn't have yet the
> dependency first, then build the latest. You can also talk to the
> maintainers, because they should know how to resolve the cyclic
> dependency properly
So, a lot of options.
Wouldn't it be better if we had a packaging guideline forcing the spec
to either have something like a %bootstrap macro, or at least contain
a comment _documenting_ how to bootstrap the package?
+1 on the guideline.
--
Darryl L. Pierce <mcpierce(a)gmail.com>
http://mcpierce.blogspot.com/
Famous last words:
"I wonder what happens if we do it this way?"