On Thu, 2004-02-26 at 20:30, Michael Schwendt wrote:
Is an URL which contains macros still an URL? What do you do with an
URL
that contains macros? You can't cut'n'paste it into a browser, because it
contains macros. So why include protocol, hostname and path in Source
fields at all? How does the packager fetch a new release? Does he visit
the web page from bookmarks? Or does he reconstruct a valid URL from
the macros?
Thanks, Michael, that's a great explanation.
I've got a new scenario to ask about: do any of the autobuilders the
Fedora Project is going to use depend on being able to parse the Source:
line into a URL?
(I thought I read something about mach using the Source line, but on
second read I see that's if you provide a bare spec, not the srpm.)
-Toshio
--
Toshio <toshio(a)tiki-lounge.com>