Commit graph

4 commits

Author SHA1 Message Date
Denis Knauf 522f100ce2 commands: do, retry, upgrade: if $CAVE unknown, use cave 2015-01-14 00:03:28 +01:00
Denis Knauf f1dee5d970 cave config does exist, so cave_commands/config was a bad idea. renamed to configs. 2014-04-06 15:45:40 +02:00
Denis Knauf f71b587c9c print-package-path: Prints path to packages. config: like eclectic config interactive. delete-unused-distfiles: it deletes distfiles of not installed packages. 2014-03-22 13:45:51 +01:00
Denis Knauf 3782f838eb Logic moved from truckle to cave.
truckle commands to cave added: `cave do`, `cave retry`, `cave upgrade`
You do not need truckle upgrade, now sudo cave upgrade works, too.
These commands do not depend on truckle, it works fine with cave-only.

Environment variables added via `/etc/profile.d/cave.sh`.
At the moment only resume-file-depended variables
(TRUCKLE_RESUME_FILE, CAVE_RESUME_OPTIONS, CAVE_RESOLVE_OPTIONS, ...)
If you use cave, the resume-file will be used automaticaly.
You do not need truckle anymore to have auto-resume-files.
But sudo will remove these from env...

Sudoers-config for cave added via `/etc/sudoers.d/cave`.
sudo will keep the same variables like defined in `/etc/profile.d/cave.sh`.
I do not know, but i think it can be a security hole.
But never allow users to use cave as root!
So, now you can use sudo, too.

These combinations of new cave-related changes will allow this:

  sudo cave upgrade
  sudo cave do
  # something went wrong?
  sudo cave retry

Only pagered it is easier with truckle:

  sudo cave -cy upgrade | less -R
  # vs.
  truckle upgrade
2013-07-10 13:37:23 +02:00