On Wed, 2008-03-05 at 13:55 -0500, Colin Walters wrote:
> Failing that, the right thing in the new system would be for the
> packaging process to include a script to transform the upstream
> version
> sequence into one compatible with RPM. Say versionscript.py. That
> will
> be run at build time on the Version: field to determine an
> RPM-compatible version which will get included into the spec.
Yes, but that script isn't going to be pretty. We're talking about some
rather hackish stuff that a human packager can pretty quickly
accomplish.
> > > > Also, we'd be forcing a hardcoded dist tag here.
> > >
> > > There's nothing hardcoded; you should be able to override it.
> >
> > + (echo -n "Release: " && echo $${release}$(DIST) ...
> >
> > You're hardcoding the value of the dist tag by default into the
> spec,
> > then generating the SRPM. That means that the SRPM will always have
> that
> > dist value, even if it is rebuilt.
>
> Oh. Doesn't it work to change $(DIST) there to be %{_dist}?
That would be much better...
> > Also, since this seems to happen on build operations, it means that
> > packages get a dist tag, even if the packager doesn't want one.
>
> Do we want packagers to have a choice?
Absolutely.
~spot
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
