1 |
On Mon, Apr 30, 2012 at 3:28 PM, Neil Bothwick <neil@××××××××××.uk> wrote: |
2 |
> On Mon, 30 Apr 2012 15:15:49 -0400, Michael Mol wrote: |
3 |
> |
4 |
>> I was thinking 'skip the fetch restriction check', but if the ebuild |
5 |
>> doesn't have the file path to retrieve, that's almost moot. It's |
6 |
>> _plausible_ one could calculate the path from the version of the |
7 |
>> package being emerged, though, so I suppose it's automateable. |
8 |
> |
9 |
> Assuming there even is a path on a publicly accessible ftp or http server |
10 |
> and not a file in a location that can only be accessed by PHP or whatever |
11 |
> code running on the server that runs after you sign over your soul. |
12 |
> |
13 |
> I'm not sure what the big deal is, so portasge skips emerging one package |
14 |
> because it can't download the distfile. So what? The previous version |
15 |
> worked OK the day before and won't suddenly break because an update is |
16 |
> available. Just download and upgrade when you have the time, casting the |
17 |
> appropriate curses for those that set the licence. |
18 |
> |
19 |
|
20 |
I agree. To me it's not much of an issue. However sometime ago when |
21 |
there was a conversation about how people update their machines I |
22 |
mentioned that I always do an |
23 |
|
24 |
emerge -fDuN @world |
25 |
|
26 |
prior to kicking off the real emerge just to ensure that when the |
27 |
build finally does start all the files are here and ready. This sort |
28 |
of issue is precisely why I do that. |
29 |
|
30 |
I know most people don't like calculating all the dependencies |
31 |
multiple times but I prefer to do so, get the files and then pretty |
32 |
much be guaranteed that the build proceeds without much attention from |
33 |
me. |
34 |
|
35 |
Cheers, |
36 |
Mark |