From 89042a56c5f3a10ad89a598176a8b14f1d718ba7 Mon Sep 17 00:00:00 2001 From: Ctibor Date: Thu, 4 Feb 2016 22:28:29 +0100 Subject: Update README for indilib drivers --- README.indilib-drivers | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/README.indilib-drivers b/README.indilib-drivers index b64b5bd..486ccf1 100644 --- a/README.indilib-drivers +++ b/README.indilib-drivers @@ -40,18 +40,20 @@ sudo emerge -v @indilib-drivers-live if you want bleeding edge drivers straight 5. If you want to install only drivers for the devices you use (as is the Gentoo way), you have to set appropriate USE flags: -Available USE flags (note that only 3rd party drivers are present, with exception of qhy-old, generic-ccd and nexstarevo. All other drivers are installed by sci-libs/indilib itself): +Available USE flags (Note that only 3rd party drivers are present. All other drivers are installed by sci-libs/indilib itself): - aagcloudwatcher - apogee - asicam + - dsi - duino - eqmod - fishcamp - fli - gphoto2 + - gpsd - maxdomeii - - dsi - - mi (live ebuild only) + - mi + - nexstarevo - qhy - qsi - sbig @@ -72,7 +74,7 @@ sci-libs/indilib-drivers gphoto2 qhy sbig sudo emerge sci-libs/indilib::brancik-overlay -6. Note that ebuilds for stable release of indilib drivers (currently 1.1.0) are keyworded unstable (~amd64, ~x86 specifically) and live source ebuilds are all masked by package.mask. You will have to unmask them during +6. Note that ebuilds for stable release of indilib drivers (currently 1.2.0) are keyworded unstable (~amd64, ~x86 specifically) and live source ebuilds are all masked by package.mask. You will have to unmask them during installation (use emerge with --autounmask-write option). See official docs if you do not know this means exactly. 7. You can use provided init script in /etc/init.d/indiserver and respective configuration file in /etc/conf.d/indiserver to set indiserver to start automatically. -- cgit v1.2.3