| 1 |
Paul de Vrieze wrote: |
| 2 |
> On Sunday 26 February 2006 22:29, Robin H. Johnson wrote: |
| 3 |
> |
| 4 |
>>On Fri, Feb 24, 2006 at 02:19:40PM +0000, Ciaran McCreesh wrote: |
| 5 |
>> |
| 6 |
>>>Side note: if the packages in question are fetch restricted, you're |
| 7 |
>>>screwed, and will not be able to add them to the tree. |
| 8 |
>> |
| 9 |
>>Actually, there is a solution for this, and it's reasonable logical. |
| 10 |
>>Don't use the same name that upstream does for the files. |
| 11 |
>> |
| 12 |
>>Simply tell the user to download X and place it in $DISTDIR renaming it |
| 13 |
>>to X-foo-bar, where's you've chosen X-foo-bar to avoid conflicts. |
| 14 |
> |
| 15 |
> |
| 16 |
> Is there any valid reason that we can't have portage do this |
| 17 |
> automatically. This particular way is very user-un-friendly. |
| 18 |
|
| 19 |
Check your mail archives for the old discussions about distfile name |
| 20 |
mangling (short version: a lot of stuff relies on distfile-name == |
| 21 |
basename(src_uri), also if at all this would only be a long term |
| 22 |
solution due to compat issues involved). |
| 23 |
|
| 24 |
Marius |
| 25 |
-- |
| 26 |
gentoo-dev@g.o mailing list |
Archives