Re: Unpackaged files checking - oddities

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Sat, 10 Jan 2015 00:27:15 -0600, Bruno Wolff III wrote:

> While working on a spec file to cause build failure if new fonts showed 
> up in a package, I noticed two oddities with the checking for unpackaged 
> files.
> 
> An unpackaged empty directory will not trigger a build failure.

That's an ordinary "unowned directory", which has never before triggered
a build failure. Else there would not have been hundreds of such issues
in packages. ;-)

It's not considered fatal, because if it's a directory with special
ownership/permissions, you would have an %attr entry for it for sure.

> If a file is covered by %exclude in the main package, but is not included 
> in any subpackage, it will not trigger a build failure.

%exclude is global per spec file, or else you would need to %exclude
a file in _all_ subpackages (in the case when deleting it in %install
would be more convenient anyway). That would cause some pain in some
packages.
-- 
devel mailing list
devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]
  Powered by Linux