| 1 |
2015-03-28 11:26 GMT-06:00 James <wireless@×××××××××××.com>: |
| 2 |
> Jc García <jyo.garcia <at> gmail.com> writes: |
| 3 |
> |
| 4 |
> |
| 5 |
>> I use /usr/bin/ebuild for this, emege run this when building, just |
| 6 |
>> run the build up to the prepare function so patches are applied if |
| 7 |
>> any, and look in /var/tmp/portage/cat/pkg/work/ for the 'prepared' |
| 8 |
>> sources. |
| 9 |
> |
| 10 |
>> # ebuild $PORTDIR/cat/pkg/pkg-00.ebuild prepare |
| 11 |
> |
| 12 |
> Ok I'll give this a whirl. |
| 13 |
> |
| 14 |
> |
| 15 |
>> I have this alias in my bashrc for using the ebuild command easily. |
| 16 |
>> alias=" sudo -u portage ebuild " |
| 17 |
> |
| 18 |
> |
| 19 |
> Correction |
| 20 |
> alias ebuild=" sudo -u portage ebuild " |
| 21 |
> |
| 22 |
> Ahhh. OK this make it so that proper file ownership is always correct? |
| 23 |
> |
| 24 |
It is just to not use root, and because the portage user has write |
| 25 |
privileges in /var/tmp/portage/ |
Archives