. This way
tar cannot be broken. Add an option to emerge, --backup or something
similar, that will automatically run quickpkg. Then make a erescue
executable that can parse the command line to figure out which
package the user wants to be rescued from, and execute the new tar
command.
--
David Stanek
On Sun, May 15, 2005 at 06:12:13PM -0700, John Myers wrote:
On Sunday 15 May 2005 16:41, david stanek wrote:
Add an option to emerge, --backup or something
similar, that will automatically run quickpkg.
If you set FEATURES=buildpkg, portage automatically makes binary packages
for you
On Sun, May 15, 2005 at 09:56:54PM -0400, David Stanek wrote:
On Sun, May 15, 2005 at 06:12:13PM -0700, John Myers wrote:
On Sunday 15 May 2005 16:41, david stanek wrote:
Add an option to emerge, --backup or something
similar, that will automatically run quickpkg.
If you set FEATURES
. The proposed erescue would still work in that case.
If erescue is a statically built binary that basically untars a
backed up copy of a package, why would it depend on Python?
--
David Stanek
www.roninds.net
GPG keyID #6272EDAF on http://pgp.mit.edu
Key fingerprint = 8BAA 7E11 8856 E148 6833
and the
application data separate. As a side effect it is easier to do
backups and my data between machines.
--
David Stanek
www.roninds.net
GPG keyID #6272EDAF on http://pgp.mit.edu
Key fingerprint = 8BAA 7E11 8856 E148 6833 655A 92E2 3E00 6272 EDAF
pgpjRBaQMR1NQ.pgp
Description: PGP signature
