Re: Making it easier to get and use pkgsrc

[Bernd Ernesti <netbsd%lists.veego.de@localhost>]

On Sun, Dec 12, 2010 at 07:58:45AM -0500, Greg Troxel wrote:
> 
> Jean-Yves Migeon <jeanyves.migeon%free.fr@localhost> writes:
> 
> > On 12.12.2010 02:56, Thomas Klausner wrote:
> >> On Sat, Dec 11, 2010 at 10:56:11PM +0100, Jean-Yves Migeon wrote:
> >>> - suppress warning when pkg_add'ing packages where build and target
> >>> system have different minor revisions (e.g. NetBSD-5.0.2 vs
> >>> NetBSD-5.1.RC4, for example)
> >> 
> >> To set a good example of coding vs. talking ;) I've improved the
> >> version check so pkg_add doesn't warn about adding packages from
> >> nearly the same opsys version.
> >> 
> >> In particular, this currently accepts (on NetBSD) any of foo_ALPHA*,
> >> foo_BETA*, foo_RC*, foo_STABLE*, foo_PATCH* the same as foo.
> >> Support for more platforms should be easy to add.
> >> 
> >> I'm not so sure about accepting 5.0 vs. 5.1, as you suggest above, so
> >> I left that out for now.
> >
> > I am all for this patch. While this is certainly problematic for !NetBSD
> > OS, I can't find a reason why it shouldn't be committed. Major revisions
> > for NetBSD should be binary compatible.
> 
> Sounds good to me.  Perhaps this logic also belongs in osabi; I've done
> a lot of rebuilds due to 5.1RC[1234].
> 
> I have the impression that 5.0 and 5.1 aren't binary compatible due to
> some X library, but I don't really understand.

Correct in that case they are not compatible so the check has to stay for
minor versions (x.y) but could be removed for tiny versions (x.y.z) because
they only get security updates. Hmm, securiy updates could affect static
binaries.

Bernd