On Mon, 30 Apr 2012 15:15:49 -0400, Michael Mol wrote:

> I was thinking 'skip the fetch restriction check', but if the ebuild
> doesn't have the file path to retrieve, that's almost moot. It's
> _plausible_ one could calculate the path from the version of the
> package being emerged, though, so I suppose it's automateable.

Assuming there even is a path on a publicly accessible ftp or http server
and not a file in a location that can only be accessed by PHP or whatever
code running on the server that runs after you sign over your soul.

I'm not sure what the big deal is, so portasge skips emerging one package
because it can't download the distfile. So what? The previous version
worked OK the day before and won't suddenly break because an update is
available. Just download and upgrade when you have the time, casting the
appropriate curses for those that set the licence.


-- 
Neil Bothwick

Who messed with my anti-paranoia shot?

Attachment: signature.asc
Description: PGP signature

Reply via email to