On mer. 18 mars 19:20:23 2020, Jack wrote:
> On 2020.03.18 18:59, Ian Zimmerman wrote:
> > After a hiatus I am trying to create my own ebuild repository again.  I
> > need a way to test the separate steps (fetch, prepare, comiple, install
> > etc.) and I would like to do all of them as a regular user (not root,
> > not portage).  I tried what I thought was the most natural attempt - run
> > the ebuild program under fakeroot, but it still breaks trying to change
> > permissions of things in PORTAGE_TMPDIR (of course override the value of
> > this variable).  I don't understand this - it looks just like what
> > fakeroot was intended to help with?  Anyway, I'm not married to
> > fakeroot,
> > just looking for a way to do these test runs.
> > 
> > I remember that I could do this the first time, a couple of years ago.
> > But I don't remember how :-(
> This is from memory - not currently tested, but I often do the various
> ebuild steps as myself, without a fakeroot, and not overriding the system
> PORTAGE_TMPDIR..  Again, from memory, as long as I opened permissions on
> PORTAGE_TMPDIR so I could create the necessary directories, I could do all
> steps as myself except for the final qmerge.  Once you create the group and
> package directories under PORTAGE_TMPDIR, there shouldn't be any problems.
> The final qmerge step clearly requires root, unless you are using a chroot
> to install somewhere other than the real system directories.
> 
> Jack

I’m also invoking ebuild as a regular user, the only thing that needs
permissions is when using git. However, you have to be part of the
portage group to do this.

alarig@pikachu ~ % ls -lhd /var/tmp/portage/
drwxrwxr-x 8 portage portage 4.0K Mar 19 08:37 /var/tmp/portage/
alarig@pikachu ~ % ebuild 
/var/db/repos/SwordArMor/net-misc/FORT-validator/FORT-validator-1.2.0.ebuild 
prepare
 * FORT-validator-1.2.0.tar.gz BLAKE2B SHA512 size ;-) ...              [ ok ]
>>> Unpacking source...
>>> Unpacking FORT-validator-1.2.0.tar.gz to 
>>> /var/tmp/portage/net-misc/FORT-validator-1.2.0/work
>>> Source unpacked in /var/tmp/portage/net-misc/FORT-validator-1.2.0/work
>>> Preparing source in 
>>> /var/tmp/portage/net-misc/FORT-validator-1.2.0/work/FORT-validator-1.2.0 ...
 * Applying FORT-validator-skip-online-test.patch ...                   [ ok ]
 * Running eautoreconf in 
'/var/tmp/portage/net-misc/FORT-validator-1.2.0/work/FORT-validator-1.2.0' ...
 * Running aclocal ...                                                  [ ok ]
 * Running autoconf --force ...                                         [ ok ]
 * Running autoheader ...                                               [ ok ]
 * Running automake --add-missing --copy --foreign --force-missing ...  [ ok ]
 * Running elibtoolize in: FORT-validator-1.2.0/
>>> Source prepared.
alarig@pikachu ~ % ls -lhd /var/tmp/portage/net-misc/FORT-validator-1.2.0/
drwxr-xr-x 6 alarig portage 4.0K Mar 19 08:38 
/var/tmp/portage/net-misc/FORT-validator-1.2.0/
 
-- 
Alarig

Reply via email to