In gentoo, there are essentially three ways to install a package through the
package manager:
1) Packages that are included in the main portage tree (that would be the
official packages of the distro)
2) Packages included in one of the layman overlays (would be like thirthd
party repos, but can be easily managed with a tool provided by the distro).
3) Packages in the local overlay of the user (would be the equivalent of
downloading a .deb package and install it manually).
I have no contact with the official gentoo team, so can't do much about option
1). However, Austin English, who also showed interest in this, might help with
that. AFAIK, he is on hollyday now. Maybe when he comes back he could help
with that. If this get fixed, gentoo users that want to install tails-installer
should just use the standard way:
$ emerge tails-installer
and that would be it (well, maybe some work should be done to allow the
installation of a package that is not marked as fully stable, but that is the
kind of things that a typical gentoo user is used to deal with)
About option 2), I also don't maintain any of those semioficial overlays.
However, one of those overlays is focused preciselly on torbrowser and related
packages. I have already sent a pull request to include my ebuild in it. If it
is merged, the installation would be almost as easy. Just install the layman
tool in the usual way and then:
$ layman -a torbrowser
$ emerge tails-installer
Finally, until 1) and/or 2) become possible, a regular user can use a local
overlay. In order to do so, (s)he should follow the following steps:
a) enable the local overlay by adding a line like
PORTDIR_OVERLAY = "/usr/local/portage/"
to the file /etc/portage/make.conf
b) copy the directory tails-installer and its content inside of the directory
/usr/local/portage/app-misc
c) run the usual "emerge tails-installer" command.
I hope this helps to clarify the general picture. If you need more details, I
would be happy to provide them.
P.S. During the writing of the ebuild I noticed that there are several
dependencies that are not listed in the README file. They are the following:
configobj
urlgrabber
python-distutils-extra
pygobject
pyparted
cdrtools
gptfdisk
best,
Miguel Marco
> Miguel Angel Marco Buzunariz:
> > I have uploaded the ebuild to
> > https://github.com/miguelmarco/tails-installer-ebuild
> >
> > If someone has access to a gentoo box, please test it.
> >
> > If furthermore someone maintains a gentoo overlay, or any other place were
> > it
> > makes sense to offer an ebuild, please feel free to include it.
>
> Hi Miguel,
>
> I never used Gentoo myself so I won't be able to test this.
>
> But I wrote the new set of installation instructions [1] and I wonder
> when and how we should document tails-installer for Gentoo in there.
>
> So, what would be the process for the official inclusion of
> tails-installer in Gentoo? What needs to happen before a regular Gentoo
> user can use your work?
>
> Once this happen, I'd like to get some basic instructions so I can maybe
> test this in a Gentoo live CD and then I'll propose something to
> document this in [1].
>
> [1]: https://tails.boum.org/install/
signature.asc
Description: This is a digitally signed message part.
___
Tails-dev mailing list
Tails-dev@boum.org
https://mailman.boum.org/listinfo/tails-dev
To unsubscribe from this list, send an empty email to
tails-dev-unsubscr...@boum.org.
