Re: [PATCH] Automatically append a semi-random version for BK users

[Ryan Anderson]

Sam, my patch to automatically include a random value based upon the
BitKeeper or CVS version in the kernel version had one, rather minor,
bug related to building in seperate object and source trees.

This patch fixes that up.

Signed-Off-By: Ryan Anderson <ryan@xxxxxxxxxxxxxx>

Index: local-quilt/scripts/setlocalversion
===================================================================
--- local-quilt.orig/scripts/setlocalversion	2005-04-02 18:29:21.000000000 -0500
+++ local-quilt/scripts/setlocalversion	2005-04-02 18:29:54.000000000 -0500
@@ -14,6 +14,7 @@ EOT
 }
 
 my ($srctree) = @ARGV;
+chdir($srctree);
 
 my @LOCALVERSIONS = ();
 
@@ -39,7 +40,6 @@ my @LOCALVERSIONS = ();
 # -BK and the above 8 characters to the end of the version.
 
 sub do_bk_checks {
-	chdir($srctree);
 	my $changeset = `bk changes -r+ -k`;
 	chomp $changeset; # strip trailing \n safely
 	my $tag = `bk prs -h -d':TAG:' -r'$changeset'`;
@@ -69,7 +69,6 @@ sub do_bk_checks {
 # On this check, there is no real need for a MD5 hash, so
 # the revision number is used directly.
 sub do_cvs_checks {
-	chdir($srctree);
 	my $status = `LANG=C cvs status -v ChangeSet`;
 	my @lines = split /\n/, $status;
 


-- 

Ryan Anderson
  sometimes Pug Majere
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/