Bug#345439: Changed wildcard handling in v5 mode
Le samedi 31 décembre 2005 à 13:51 -0500, Joey Hess a écrit : > This was changed in 4.9.5: > > * dh_install: in v5 mode, error out if there are wildcards in the file > list and the wildcards expand to nothing. Done only for v5 as this is a > behavior change. Closes: #249815 > > The old behavior was never intended to allow file exclusion; it was just a > bug. I've documented it in the man page now. > > There's currently not a way to conditionally install a file with dh_install > except stuff like this: > > -dh_install debian/tmp-amd64/usr/lib*/librpcsvc.a* usr/lib64 > Ah, okay. Thanks. I used to rely on this behavious quite heavily. As a feature request for v6 mode, will you consider changing these to be regular expressions with an option to allow a "zero match" mode? The problem I'm trying to solve with glibc is that I have a list of .a files. Most of which I want. One of which might not get generated under some circumstances, and 4 or 5 of which should not be in this package because they're profiling libraries (*._p.a). Listing them is annoying because the list of libraries that glibc ships changes as add-ons are changed, or as the library changes over time. Tks, Jeff Bailey signature.asc Description: Ceci est une partie de message numériquement signée
Bug#345439: Changed wildcard handling in v5 mode
Jeff Bailey wrote: > When updating glibc to use debhelper v5 mode instead of v4 mode, I > discovered that the line: > > debian/tmp-amd64/usr/lib*/librpcsvc.a* usr/lib64 > > No longer works for excluding a file. This file is only produced when > natively compiling glibc, but not when cross compiling. We generate the > debhelper install lists from some master versions. In v4 mode, the > wildcard matches nothing as well and debhelper continues on. In v5 > mode, I now get an abort because the file doesn't exist. > > I realize that this might not actually be a bug, but if not then the > changed globbing handling should be documented in the debhelper manpage > as a change from v5. If that's also the case, can you suggest the > current Best Practice for listing a file that might not be there? This was changed in 4.9.5: * dh_install: in v5 mode, error out if there are wildcards in the file list and the wildcards expand to nothing. Done only for v5 as this is a behavior change. Closes: #249815 The old behavior was never intended to allow file exclusion; it was just a bug. I've documented it in the man page now. There's currently not a way to conditionally install a file with dh_install except stuff like this: -dh_install debian/tmp-amd64/usr/lib*/librpcsvc.a* usr/lib64 -- see shy jo signature.asc Description: Digital signature
Bug#345439: Changed wildcard handling in v5 mode
Package: debhelper Version: 5.0.7 When updating glibc to use debhelper v5 mode instead of v4 mode, I discovered that the line: debian/tmp-amd64/usr/lib*/librpcsvc.a* usr/lib64 No longer works for excluding a file. This file is only produced when natively compiling glibc, but not when cross compiling. We generate the debhelper install lists from some master versions. In v4 mode, the wildcard matches nothing as well and debhelper continues on. In v5 mode, I now get an abort because the file doesn't exist. I realize that this might not actually be a bug, but if not then the changed globbing handling should be documented in the debhelper manpage as a change from v5. If that's also the case, can you suggest the current Best Practice for listing a file that might not be there? Tks, Jeff Bailey signature.asc Description: Ceci est une partie de message numériquement signée
