On May 14, 2009, at 12:20 PM, Per Øyvind Karlsen wrote:
Well, bloat wasn't really the issue, but rather build breakages.
If mandatory then configure should check for the headers.
Well there are two ways to fix that, enable or disable:
1) add the ususal #ifdef WITH_KEYUTILS
2) change
2009/5/14 Jeff Johnson
>
> On May 14, 2009, at 11:53 AM, Per Øyvind Karlsen wrote:
>
>>
>> btw. I noticed rpm building rpmkey & rpmxar by default now for
>> some reason? (didn't happen with HEAD)
>> How does one disable the build of these if headers missing?
>>
>
> One doesn't disable rpmkey or r
On May 14, 2009, at 11:53 AM, Per Øyvind Karlsen wrote:
btw. I noticed rpm building rpmkey & rpmxar by default now for
some reason? (didn't happen with HEAD)
How does one disable the build of these if headers missing?
One doesn't disable rpmkey or rpmxar or luac/luav or js or Berkeley
DB util
2009/5/14 Jeff Johnson
> Thanks for doing.
>
> But somehow there has to be a better way to
> include files (and sub-trees) in EXTRA_DIST without
> explicitly enumerating each and every file.
>
> E.g. liveconnect is unused by rpmjs, and is highly unlikely
> to ever be used. Meanwhile the cost of c
On May 14, 2009, at 11:41 AM, Jeff Johnson wrote:
I haven't a clue what the better answer is.
But the explicit enumeration is likely to break
again and again and again. I know my habits well ;-)
I perhaps should mention the original reason for
explicit enumeration of files.
When releasing
Thanks for doing.
But somehow there has to be a better way to
include files (and sub-trees) in EXTRA_DIST without
explicitly enumerating each and every file.
E.g. liveconnect is unused by rpmjs, and is highly unlikely
to ever be used. Meanwhile the cost of customizing
imported subtrees is non-tr