| View previous topic :: View next topic |
| Author |
Message |
pi-cubic
Tux's lil' helper
Joined: 25 May 2003
Posts: 143
|
 Posted: Tue Jun 06, 2006 12:56 am Post subject: install gentoo in your $HOME? |
 |
|
hi, is there a lightweight gentoo distribution, optimized for a installation under your $HOME directory? it shouldn't consume a lot of space. it should behave like a --prefixe=$HOME installation.
greets,
pi-cubic |
|
| Back to top |
|
 |
Beefrum
Apprentice
Joined: 23 May 2006
Posts: 234
|
| Posted: Tue Jun 06, 2006 1:15 am Post subject: |
|
|
Sounds like user-mode linux to me. Not with a current gentoo setup available. At least not to my knowledge. 
Last edited by Beefrum on Sun Jul 23, 2006 6:26 pm; edited 1 time in total |
|
| Back to top |
|
|
pi-cubic
Tux's lil' helper
Joined: 25 May 2003
Posts: 143
|
| Posted: Tue Jun 06, 2006 1:26 am Post subject: |
|
|
| no, UML is very different. I meant a gentoo installation on any $HOME, not a system in a system. |
|
| Back to top |
|
|
Beefrum
Apprentice
Joined: 23 May 2006
Posts: 234
|
| Posted: Tue Jun 06, 2006 1:33 am Post subject: |
|
|
As some discussions want to repeat themselves, what is it good for. 
Last edited by Beefrum on Sun Jul 23, 2006 6:27 pm; edited 1 time in total |
|
| Back to top |
|
|
Beefrum
Apprentice
Joined: 23 May 2006
Posts: 234
|
|
| Back to top |
|
|
pi-cubic
Tux's lil' helper
Joined: 25 May 2003
Posts: 143
|
| Posted: Tue Jun 06, 2006 5:14 pm Post subject: |
|
|
| you are right, your pointer describes EXACTLY what i was looking for. Seems so for nobody has found a satisfying solution yet... |
|
| Back to top |
|
|
GNUtoo
Veteran
Joined: 05 May 2005
Posts: 1919
|
| Posted: Sun Jul 23, 2006 12:22 pm Post subject: |
|
|
| so you want a prefixed portage in your home? |
|
| Back to top |
|
|
pi-cubic
Tux's lil' helper
Joined: 25 May 2003
Posts: 143
|
| Posted: Sun Jul 23, 2006 12:51 pm Post subject: |
|
|
Indeed. As I said, since there is usually a quota on many administered $HOMEs, it should be bare and slim. I simply want some basic applications in my home which are easy to compile with ./config --prefix=$HOME && make && make install. Yet, some applications have big and cumbersome tail of dependencies. I don't want to spend days of trying the right library combinations, a simple emerge <package> should be able to install the <package> in my $HOME. Does such a gentoo branch exist?
pi3 |
|
| Back to top |
|
|
GNUtoo
Veteran
Joined: 05 May 2005
Posts: 1919
|
| Posted: Mon Jul 24, 2006 10:54 am Post subject: |
|
|
it is normaly possible to do that because the macOS architecture is a prefixed portage
but i don't know how to do it
mabe look at the macos installatoin guide |
|
| Back to top |
|
|
GNUtoo
Veteran
Joined: 05 May 2005
Posts: 1919
|
| Posted: Tue Jul 25, 2006 3:32 am Post subject: |
|
|
| mabe look also at all port to strange kernels such as gnu/KfreeBSD,solaris... SFU if there are some thing about prefixed portage |
|
| Back to top |
|
|
Headrush
Watchman
Joined: 06 Nov 2003
Posts: 5597
Location: Bizarro World
|
| Posted: Tue Jul 25, 2006 3:56 am Post subject: |
|
|
This doesn't seem very practical, but technically, you could compile and program in your home directory after setting up needed missing libraries and proper path variable as needed.
I think something like klik is probably what you need. Since you said you only had a handful of small apps, the static nature of klik images shouldn't be a problem.
I don't know what DE the university uses, or if klik works with Gnome/other DEs, but is that what you are looking for?
(I don't think you can ever expect being about to use portage to emerge into a user's directory.) |
|
| Back to top |
|
|
tcx
n00b
Joined: 23 Mar 2005
Posts: 32
Location: Porto, Portugal
|
| Posted: Tue Aug 22, 2006 7:36 pm Post subject: |
|
|
You could try using these options:
| Quote: | ENVIRONMENT OPTIONS
ROOT = [path]
Use ROOT to specify the target root filesystem to be used for merging packages or ebuilds.
Defaults to /.
PORTAGE_CONFIGROOT = [path]
Use PORTAGE_CONFIGROOT to specify the location for various portage configuration files (see FILES for a detailed list).
Defaults to /.
|
So, having these while emerging would read the files
| Quote: | FILES
/var/lib/portage/world
Contains a list of all user-specified packages. You can safely edit this file, adding packages that you want to be considered
in world set updates and removing those that you do not want to be considered.
/etc/make.conf
Contains variables for the build process, overriding those in make.globals. You should edit this file instead of the ones
listed below.
/etc/dispatch-conf.conf
Contains settings to handle automatic updates/backups of configuration files.
/etc/make.profile/make.defaults
Contains profile-specific variables for the build process. Do not edit this file.
/etc/make.profile/use.defaults
Contains a list of packages which, if installed, cause the respective USE flag to be enabled by default. Do not edit this file.
/usr/portage/profiles/use.desc
Contains the master list of USE flags with descriptions of their functions. Do not edit this file.
/etc/make.profile/virtuals
Contains a list of default packages used to resolve virtual dependencies. Do not edit this file.
/etc/make.profile/packages
Contains a list of packages used for the base system. The system and world sets consult this file. Do not edit this file.
/etc/make.globals
Contains the default variables for the build process. Do not edit this file.
|
from your PORTAGE_CONFIGROOT dir and would install to ROOT dir.
Take $FAKEROOT as your new root in your home, say gentoo.
I have played with the ROOT env option sometimes and it creates at the new ROOT dir the /var/db/pkg/ dir structure after installing the files. It also considers it when calculating dependencies.
You have 2 options, if your root system is a gentoo system and you are in the portage group, you can emerge --pretend the packages you want to install in your home and then install them with the new env settings using | Code: | | ebuild $HOME/$FAKEROOT/usr/portage/xxx-yyy/kkk/kkk-0.0.0.ebuild merge |
or if your root is not a gentoo system you have another 2 options:
check for the dependencies yourself and ebuild as above by the order necessary and considering you have done all dependency checkings for every package to ebuild or ebuild an empty system. This, of course, would emerge everything (glibc, gcc, etc...) but could be done using the emerge command instead of manual ebuild commands.
Keeping it minimal, I have just tried the first option and it worked. I have tried it mounting /usr/portage , /etc and /var/lib/portage from the root filesystem in my $HOME/$FAKEROOT/* .
I have installed eix using
| Code: | | ROOT="$HOME/$FAKEROOT" PORTAGE_CONFIGROOT="$HOME/$FAKEROOT" ebuild $HOME/FAKEROOT/usr/portage/app-portage/eix/eix-0.6.4.ebuild merge |
Please remember that after all, you'll have to update your PATH variable
like, | Code: | | export PATH=$HOME/$FAKEROOT/usr/bin:$PATH |
so that you programs come first in the PATH search line.
This way you can install and uninstall packages safely. Dependencies are always a problem, since you have a quota in you $HOME, a bigger one...
It should work but not without some effort. I really don't know a better approach but I am rather n00b.
Well, hope it helped...
P.S.:
This kind of install is exactly as the pkgsrc package system.
You can untar it in /usr and it creates a pkgsrc dir. You bootsrapt it and it is ready to use.
You just have to | Code: | | cd pkgsrc/category/program/ |
and and the program is installed to the pkgsrc dir considering some (I really don't know how much) of the programs and libraries you have installed in you root filesystem.
So it doesn't touch ANY of the root filesystem you had prior to installing pkgsrc to you /usr dir.
To use the pkgsrc programs all you have to do is to update your PATH as above.
This might not be accurate because I've tried it only a couple of times... |
|
| Back to top |
|
|
tcx
n00b
Joined: 23 Mar 2005
Posts: 32
Location: Porto, Portugal
|
| Posted: Tue Aug 22, 2006 10:38 pm Post subject: |
|
|
| BTW, I stumbled across this. |
|
| Back to top |
|
|
|
Gentoo on Alternative Architectures
