public inbox for linux-btrfs@vger.kernel.org
 help / color / mirror / Atom feed
From: Duncan <1i5t5.duncan@cox.net>
To: linux-btrfs@vger.kernel.org
Subject: Re: failed to read the system array on sdX
Date: Wed, 22 Jan 2014 16:18:31 +0000 (UTC)	[thread overview]
Message-ID: <pan$1d6c4$b8303dbf$82032e51$ec0030c7@cox.net> (raw)
In-Reply-To: CAD_cGvHMX0=EaThq3u_ZOGGcXgi0hmmW-_zUVf5WK5dEzPg2vQ@mail.gmail.com

Hans-Kristian Bakke posted on Tue, 21 Jan 2014 23:09:58 +0100 as
excerpted:

> 2. There is no uninstall target in the btrfs-tools Makefile. How am I
> supposed to uninstall btrfs-progs if wanting to go back to older
> versions (or newer)?

As I run gentoo not debian, I won't try to answer the other.  However I 
can answer this, to /some/ extent anyway.

a) (probably not all that interesting to you) On gentoo there's a live-
git ebuild available.  The PM will track the files it installs just as it 
would for any other package.  (A fake-install to a temp location is done 
first and the files that appear there are automatically registered for 
tracking and later uninstall.  Then the fake install is copied to the 
live filesystem.)  If your distro has something similar...

b) As is often the case with in-development "leaf" packages that are 
mostly executables and documentation (that is, no libraries/headers/etc 
that other packages will need), a standard recommendation is to use the 
files directly from the build dir, without actually installing.

So you'd build btrfs, and any time you wanted to use it you'd simply cd 
to its build dir and do ./btrfs (or other command).  Then you'd simply 
delete the build dir to uninstall.

Of course you could manually copy individual files out of the build dir, 
say to your initr* build, if desired, and track the ones you did just as 
manually.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman


      reply	other threads:[~2014-01-22 16:18 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21 21:31 failed to read the system array on sdX Hans-Kristian Bakke
2014-01-21 22:09 ` Hans-Kristian Bakke
2014-01-22 16:18   ` Duncan [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='pan$1d6c4$b8303dbf$82032e51$ec0030c7@cox.net' \
    --to=1i5t5.duncan@cox.net \
    --cc=linux-btrfs@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox