| 1 |
On Tue, May 25, 2004 at 11:17:55PM +0200, Carsten Lohrke wrote: |
| 2 |
> -----BEGIN PGP SIGNED MESSAGE----- |
| 3 |
> Hash: SHA1 |
| 4 |
> |
| 5 |
> On Tuesday 25 May 2004 22:47, Ajai Khattri wrote: |
| 6 |
> > Just wondering how people handle projects hosted on sourceforge in an |
| 7 |
> > ebuild as far as downloading tarballs is concerned? When you download from |
| 8 |
> > sourceforge you are redirected to a page which allows you to select your |
| 9 |
> > nearest mirror. How could (should?) this be handled in an ebuild? |
| 10 |
> |
| 11 |
> |
| 12 |
> HOMEPAGE="http://<FOO>.sourceforge.net/" |
| 13 |
> SRC_URI="mirror://sourceforge/<FOO>/${P}.tar.gz" |
| 14 |
> |
| 15 |
> Have a look at /usr/portage/profiles/thirdpartymirrors for other supported |
| 16 |
> mirror lists. Often you don't want to search the standard mirrors, but only |
| 17 |
> the defined mirrors in SRC_URI. To achieve this, add |
| 18 |
> |
| 19 |
> RESTRICT="nomirror" |
| 20 |
> |
| 21 |
> to the ebuild. |
| 22 |
|
| 23 |
Just use RESTRICT=nomirror when the file is massive (many hundreds of |
| 24 |
megabytes) or we're legally prohibited from redistributing it. |
| 25 |
|
| 26 |
-- |
| 27 |
Jon Portnoy |
| 28 |
avenj/irc.freenode.net |
| 29 |
|
| 30 |
-- |
| 31 |
gentoo-dev@g.o mailing list |
Archives