* The reporting can probably be improved: aka, highlight blocks with
potential issues better. For example, embed relevant portions of an XSA
into the output in cases where there is no match
-* --xsadir currently only works when providing an absolute path (the issue
- was introduced in commit 6d371d6adccc36eeeb5d2acd412ba0f3424a4a15)
xsa.git:Infra/xsa-list-patches
------------------------------
my $XSAFILE;
my $XSADIR;
my $XSAFETCH;
-my $LOGROOT = File::Spec->canonpath(cwd()."/../xen-release-logs" );
+my $LOGROOT = "../xen-release-logs";
GetOptions(
'version=s' => \$VERSION,
# Set up XSADIR and XSAFETCH, if not set
if (!$XSADIR && $SMART!=0) {
$XSAFETCH = "https://xenbits.xenproject.org/xsa/";
- $XSADIR = File::Spec->canonpath(cwd()."/../xsaweb" );
+ $XSADIR = "../xsaweb";
system("rm -rf $XSADIR");
mkdir $XSADIR;
}
-
+
+# Make relative paths absolute
+$LOGROOT = File::Spec->rel2abs($LOGROOT);
+$XSADIR = File::Spec->rel2abs($XSADIR);
+
# Directories
if (! -e $LOGROOT) {
mkdir $LOGROOT;