tech-pkg archive

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]

Re: Easiest way to compare pkg versions?



Jonathan Perkin transcribed 929 bytes:
> * On 2019-04-10 at 17:00 BST, John Klos wrote:
> 
> > Given a pkgsrc directory for a package (say, shells/tcsh) and a binary
> > package (tcsh-6.20.00nb2.tgz, for example), what's the easiest way to
> > determine whether the binary package is up to date compared with the pkgsrc
> > directory?

If you want to build the directory for the package again and the
binary package is not in packages/All/$name, and you want a verbose
look, you could use diffoscope[1]. Although this might be overkill for
just knowing if it's up to date.
 
1: https://diffoscope.org/ (I think it is sysutils/py-diffoscope)

> Depends on your definition of "up to date".  If you only care about
> the version then just compare PKGNAME vs the .tgz.
> 
> However, if you care about it being up to date compared to whether its
> dependencies have been rebuilt and/or whether files have been touched
> without the version being changed, then you could start with the pbulk
> script that performs those checks:
> 
>   pkgsrc/pkgtools/pbulk/files/pbulk/scripts/pkg-up-to-date
> 
> That only tests files that have $NetBSD$ tags, so if you have dropped
> something in FILESDIR that isn't in CVS you'll need to expand the
> script a bit further.
> 
> -- 
> Jonathan Perkin  -  Joyent, Inc.  -  www.joyent.com
> 


Home | Main Index | Thread Index | Old Index