| 1 |
On Tue, 03 Nov 2015 11:51:53 -0600 |
| 2 |
Alex Brandt <alunduil@g.o> wrote: |
| 3 |
|
| 4 |
> On Tuesday, November 03, 2015 12:29:01 Joakim Tjernlund wrote: |
| 5 |
> > Sometimes I have to move files from my layman overlays distfiles to |
| 6 |
> > /usr/portage/distfiles in orders to rebuild older stuff not in |
| 7 |
> > gentoo anymore. |
| 8 |
> |
| 9 |
> Wouldn't it be better to fix the ebuilds in the overlay to point at a |
| 10 |
> current URL for the tarball? |
| 11 |
> |
| 12 |
> > Should not emerge search in distfiles where the ebuild resides? |
| 13 |
> |
| 14 |
> No, the ebuild should specify where to get the tarball. |
| 15 |
> |
| 16 |
> Not sure these comments are what you're looking for but it sounds |
| 17 |
> like you just need to fix the ebuilds in your overlay to point at the |
| 18 |
> distfiles in your overlay as a SRC_URI. |
| 19 |
> |
| 20 |
> Just my 2ยข, disregard if too assumptive. |
| 21 |
> |
| 22 |
> Regards, |
| 23 |
> |
| 24 |
|
| 25 |
It is entirely possible for an ebuild to install a pkg from sources |
| 26 |
only from the pkg's files directory. Provided the sources are within |
| 27 |
the size limits for the files directory. Although an overlay may be |
| 28 |
allowed to go past that for a non-gentoo tree pkg & ebuild. |
| 29 |
|
| 30 |
-- |
| 31 |
Brian Dolbec <dolsen> |
Archives