2011/1/27 Ben Walton <[email protected]>: > Maciej, what is checkpkg doing in this regard currently? Does it > check for this string at all? If so, does it check every file or only > certain areas?
When I noticed that packages are rejected because of /usr/local references, I added the "/usr/local" string to the content blacklist. The change was made in r13006[1]. Previously, checkpkg has been checking for /export/medusa and /opt/build. I started working on the version of checkpkg checked into gar tree, updated by comand in revision 1841. Currently, there is no distinction between paths in checkpkg. If a file contains the string, an error is thrown. We could add more logic to alter the behavior depending on whether files with bad content are in docdir or elsewhere, but there are also other options: - if the offending string is found in the doc directory, and the files in question are text/html/xml files, it's safe to sed to replace all paths - if the maintainer does not wish to run sed, the error can be overridden Maciej [1] http://sf.net/apps/trac/gar/browser/csw/mgar/gar/v2/lib/python/package_stats.py?annotate=blame [2] http://sf.net/apps/trac/gar/browser/csw/trunk/bin/checkpkg?rev=1841 _______________________________________________ maintainers mailing list [email protected] https://lists.opencsw.org/mailman/listinfo/maintainers .:: This mailing list's archive is public. ::.
