Macros in Source fields (was: Re: Prelink success story :))

[Panu Matilainen]

On Fri, 27 Feb 2004, Michael Schwendt wrote:

> On Thu, 26 Feb 2004 21:33:49 -0500, Toshio wrote:
> 
> > 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 doubt that.

IIRC mach can parse Source and Patch entries (even in presence of macros), 
fetch what's needed and build based on that. Actually if those entries 
aren't URL's it's going to fail, unless you use rebuild (to rebuild from 
existing src.rpm)

	- Panu -