[pacman-dev] Feature request: Dependency versions in .SRCINFO

Dave Reisner d at falconindy.com
Fri Dec 19 23:18:55 UTC 2014

On Sat, Dec 20, 2014 at 12:02:56AM +0100, David Macek wrote:
> On 19. 12. 2014 23:09, Dave Reisner wrote:
> > On Fri, Dec 19, 2014 at 10:50:46PM +0100, David Macek wrote:
> >> Hi all.
> >>
> >> I'd like to propose including package versions in the list of package dependencies (both depends and makedepends) in .SRCINFO. The versions would be the ones currently installed on the system makepkg is running on. The goal is to provide more information about the environment where the package was built (for example to check if the dependencies were up to date at the time of the build).
> >>
> >> I'm not sure if this is useful in Arch Linux use cases (it seems from my IRC conversations that every package in Arch is rebuilt once its dependencies are updated), but I hope someone else could consider this a useful feature.
> >>
> >> I'm not sure if the information is better provided in .PKGINFO, .SRCINFO, or both.
> >
> > If you have such dependencies, why are they not expressed in the PKGBUILD?
> I don't get how that would help. Maybe I expressed myself wrong. Let's say foo depends on bar (but doesn't specify any version requirements for this dependency). foo version 1.0 was built with bar 0.2 and uploaded to the repository. I would like to be able to download the package and sourceball of foo 1.0 and see something like "depend = bar # built with bar 0.2" instead of just "depend = bar" in .{PKG,SRC}INFO.
> One use case could be -- when bar 0.3 comes out -- to check if foo was rebuilt with the new bar.
> -- 
> David Macek

I see. This is outside the realm of what SRCINFO was intended for -- a
parseable copy of the PKGBUILD. What you're asking for could just as
easily be collected and catalogued external to the build process. The
SRCINFO does help you here, though, as it does the hard part (parsing
bash) for you.

Does that clarify?

More information about the pacman-dev mailing list