Lintian::Processable::Patched (3) - Linux Manuals
Lintian::Processable::Patched: access to sources with Debian patches applied
NAME
Lintian::Processable::Patched - access to sources with Debian patches applied
SYNOPSIS
use Lintian::Processable;
my $processable = Lintian::Processable::Binary->new;
DESCRIPTION
Lintian::Processable::Patched provides an interface to collected data about patched sources.INSTANCE METHODS
- patched
- Returns a index object representing a patched source tree.
- index (FILE)
-
The index of a source package is not very well defined for non-native
source packages. This method gives the index of the ``unpacked''
package (with 3.0 (quilt), this implies patches have been applied).
If you want the index of what is listed in the upstream orig tarballs, then there is ``orig_index''.
For native packages, the two indices are generally the same as they only have one tarball and their debian packaging is included in that tarball.
IMPLEMENTATION DETAIL/CAVEAT: Lintian currently (2.5.11) generates this by running ``find(1)'' after unpacking the source package. This has three consequences.
First it means that (original) owner/group data is lost; Lintian inserts ``root/root'' here. This is usually not a problem as owner/group information for source packages do not really follow any standards.
Secondly, permissions are modified by A) umask and B) laboratory set{g,u}id bits (the laboratory on lintian.d.o has setgid). This is *not* corrected/altered. Note Lintian (usually) breaks if any of the ``user'' bits are set in the umask, so that part of the permission bit should be reliable.
Again, this shouldn't be a problem as permissions in source packages are usually not important. Though if accuracy is needed here, ``orig_index'' may used instead (assuming it has the file in question).
Third, hardlinking information is lost and no attempt has been made to restore it.
Needs-Info requirements for using index: unpacked
- sorted_index
-
Returns a sorted array of file names listed in the package. The names
will not have a leading slash (or ``./'') and can be passed to
``unpacked ([FILE])'' or ``index (FILE)'' as is.
The array will not contain the entry for the ``root'' of the package.
- index_resolved_path(PATH)
-
Resolve PATH (relative to the root of the package) and return the
entry denoting the resolved path.
The resolution is done using resolve_path.