Re: getting rid of the .changes requirements

[Alexander Reichle-Schmehl <tolimar@debian.org>]

Hi!

* Gerfried Fuchs <rhonda@deb.at> [130812 11:15]:
> > Better support in the building front-end tools could help.  At least in
> > theory, debian/changelog says what distribution you're targetting when you
> > build.  Given that information, one could make an rmadison call to find
> > the current version of the package in that distribution (or, for
> > *-backports, when the package isn't found, the associated base
> > distribution) and then add the appropriate -v flag automatically.
> > 
> > It would require a dependency on rmadison, so it's probably not something
> > for dpkg-buildpackage, but debuild, pdebuild, git-buildpackage, or
> > anything else that's higher in the dependency stack should be fair game.
>  Interesting idea, it though would also require network in the build
> environment, which isn't always available. :)

I'm jumping into the discussion, so I might be missing something, by why
do you need rmadison at all?

You'll have to build the package in a stable+backports build environment
anyway, so the problem can be solved with the data of "apt-cache policy"
or similar. If there's a backported package: You have the
last version number. It there's no backported package: Take the version from
stable.

That should also work in buildds, shouldn't it?


Best regards,
  Alexander