On Thu, Jun 29, 2017 at 08:33:46AM +0100, Neal Gompa wrote:
> On Thu, Jun 22, 2017 at 10:20 PM, Darren Hart (VMware)
> wrote:
> > Introduce a --disable-bdb configuration option which disables the use of
> > Berkeley DB entirely. Update the various autotools to ensure that at
On Thu, Jun 22, 2017 at 10:20 PM, Darren Hart (VMware)
wrote:
> Introduce a --disable-bdb configuration option which disables the use of
> Berkeley DB entirely. Update the various autotools to ensure that at
> least one of BDB or NDB is enabled. Existing configuration
I don't see how this change would affect that use case at all. Before this
change, the macros were expanded using `%{__python}`, and they still are (the
shebang in the scriptlet is not used).
--
You are receiving this because you are subscribed to this thread.
Reply to this email directly or
Change the generation of build-id files to a file list using ARGV_t.
First go through the current package list and generate a files list.
Then add those files as if they were part of the original package file
list using the new resetPackageFilesDefaults() and addPackageFileList().
Signed-off-by:
mkattr used "-" as default mode which would pick up the mode for files
as they were on disk. This could cause files generated by rpmbuild to
use a "non-standard" mode if umask was set by the user. Explitictly
use 755 for directories and 644 for files to make builds independent
of any umask
Extract two functions resetPackageFilesDefaults() and addPackageFileList()
from processPackageFiles(). This will make it possible to add multiple
(generated) file lists to a package later.
Signed-off-by: Mark Wielaard
---
build/files.c | 170