1 |
On mer. 18 mars 19:20:23 2020, Jack wrote: |
2 |
> On 2020.03.18 18:59, Ian Zimmerman wrote: |
3 |
> > After a hiatus I am trying to create my own ebuild repository again. I |
4 |
> > need a way to test the separate steps (fetch, prepare, comiple, install |
5 |
> > etc.) and I would like to do all of them as a regular user (not root, |
6 |
> > not portage). I tried what I thought was the most natural attempt - run |
7 |
> > the ebuild program under fakeroot, but it still breaks trying to change |
8 |
> > permissions of things in PORTAGE_TMPDIR (of course override the value of |
9 |
> > this variable). I don't understand this - it looks just like what |
10 |
> > fakeroot was intended to help with? Anyway, I'm not married to |
11 |
> > fakeroot, |
12 |
> > just looking for a way to do these test runs. |
13 |
> > |
14 |
> > I remember that I could do this the first time, a couple of years ago. |
15 |
> > But I don't remember how :-( |
16 |
> This is from memory - not currently tested, but I often do the various |
17 |
> ebuild steps as myself, without a fakeroot, and not overriding the system |
18 |
> PORTAGE_TMPDIR.. Again, from memory, as long as I opened permissions on |
19 |
> PORTAGE_TMPDIR so I could create the necessary directories, I could do all |
20 |
> steps as myself except for the final qmerge. Once you create the group and |
21 |
> package directories under PORTAGE_TMPDIR, there shouldn't be any problems. |
22 |
> The final qmerge step clearly requires root, unless you are using a chroot |
23 |
> to install somewhere other than the real system directories. |
24 |
> |
25 |
> Jack |
26 |
|
27 |
I’m also invoking ebuild as a regular user, the only thing that needs |
28 |
permissions is when using git. However, you have to be part of the |
29 |
portage group to do this. |
30 |
|
31 |
alarig@pikachu ~ % ls -lhd /var/tmp/portage/ |
32 |
drwxrwxr-x 8 portage portage 4.0K Mar 19 08:37 /var/tmp/portage/ |
33 |
alarig@pikachu ~ % ebuild /var/db/repos/SwordArMor/net-misc/FORT-validator/FORT-validator-1.2.0.ebuild prepare |
34 |
* FORT-validator-1.2.0.tar.gz BLAKE2B SHA512 size ;-) ... [ ok ] |
35 |
>>> Unpacking source... |
36 |
>>> Unpacking FORT-validator-1.2.0.tar.gz to /var/tmp/portage/net-misc/FORT-validator-1.2.0/work |
37 |
>>> Source unpacked in /var/tmp/portage/net-misc/FORT-validator-1.2.0/work |
38 |
>>> Preparing source in /var/tmp/portage/net-misc/FORT-validator-1.2.0/work/FORT-validator-1.2.0 ... |
39 |
* Applying FORT-validator-skip-online-test.patch ... [ ok ] |
40 |
* Running eautoreconf in '/var/tmp/portage/net-misc/FORT-validator-1.2.0/work/FORT-validator-1.2.0' ... |
41 |
* Running aclocal ... [ ok ] |
42 |
* Running autoconf --force ... [ ok ] |
43 |
* Running autoheader ... [ ok ] |
44 |
* Running automake --add-missing --copy --foreign --force-missing ... [ ok ] |
45 |
* Running elibtoolize in: FORT-validator-1.2.0/ |
46 |
>>> Source prepared. |
47 |
alarig@pikachu ~ % ls -lhd /var/tmp/portage/net-misc/FORT-validator-1.2.0/ |
48 |
drwxr-xr-x 6 alarig portage 4.0K Mar 19 08:38 /var/tmp/portage/net-misc/FORT-validator-1.2.0/ |
49 |
|
50 |
-- |
51 |
Alarig |