I thought I would update the Gentoo installation instructions. If approved of, could someone replace the Get Indi/Gentoo page ?

---

0. Open a terminal, use root or sudo.

1. Install `app-eselect/eselect-repository` to manage overlays if don't have this tool already.


emerge -v app-eselect/eselect-repository

2. Add `hamari` overlay. See wiki.gentoo.org/wiki/Eselect/Repository for details.

eselect repository enable hamari
emaint sync -r hamari

3. To install indilib drivers


4. Pick your drivers from the list below and

edit/add to:

/etc/portage/make.conf

INDILIB_DRIVERS="celestronaux aagcloudwatcherng gphoto eqmod asi"

This will pull in the drivers you specify when you emerge sci-libs/indilib-drivers. USE flags are no longer used.

Driver List:

aagcloudwatcherng
ahpxc
aok
apogee
armadillo
astrolink4
astromechfoc
asi
asipower
atik
avalon
beefocus
bresserexos2
celestronaux
dreamfocuser
dsi
duino
eqmod
ffmv
fishcamp
fli
gige
gphoto2
gpsd
gpsnmea
inovaplx
limesdr
maxdomeii
mgen
mi
nexdome
nightscape
orion-ssg3
pentax
playerone
qhy
qsi
rtklib
sbig
shelyak
spectracyber
starbook
starbookten
sv305
sx
talon6
toupbase
webcam

If you wish to use ONLY the indilib packages from the hamari repository then
edit /etc/portage/package.mask and add:

*/*::hamari

This will mask all hamari packages, then edit to add in
/etc/portage/package.unmask

sci-libs/indilib::hamari

This will have to be done for all drivers you add if you go this route, vs leaving the hamari repository unmasked.

From the list above the format seems to be:

sci-libs/indilib-driver-<driver-name>

[Example /etc/portage/package.unmask file]

sci-libs/indilib-drivers::hamari
sci-libs/indilib-driver-asi::hamari
sci-libs/indilib-driver-asi-power::hamari
sci-libs/indilib-driver-eqmod::hamari
sci-libs/indilib-driver-celestronaux::hamari
sci-libs/indilib-driver-gphoto::hamari
sci-libs/libasi::hamari

All of the above files, regardless of whether the hamari repository is masked or not, if you have an amd64 stable system (vs ~amd64 unstable) will have to be added to the file

/etc/portage/package.accept_keywords/sci-libs


sci-libs/indilib-drivers::hamari ~amd64
sci-libs/indilib-driver-asi::hamari ~amd64
sci-libs/indilib-driver-asi-power::hamari ~amd64
sci-libs/indilib-driver-eqmod::hamari ~amd64
sci-libs/indilib-driver-celestronaux::hamari ~amd64
sci-libs/indilib-driver-gphoto::hamari ~amd64
sci-libs/libasi::hamari ~amd64

If you do have asi equipment, and maybe some other brands, it will be necessary to accept the license.

An example for ZWO equipment needing the file sci-libs/libasi accepted:


Edit /etc/portage/package.license to add:

sci-libs/libasi zwo-asi


You are now ready to emerge emerge -av sci-libs/indilib-drivers

If you have the correct driver file names, which seem to follow the format

sci-libs/indilib-driver-<driver-name>

then all will proceed. If not make adjustments to the package.unmask and package.accept_keywords/sci-lib files

Read More...