tech-pkg archive

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

Re: Suppressing version warning for binary package installs?



On Tue, 22 Sep 2009 21:48:10 +0900, Justin C. Sherrill 
<justin%shiningsilence.com@localhost> wrote:

DragonFly recently released version 2.4, but binary packages built for the
development releases of 2.3.1 and 2.3.2 still work for it.  However,
people adding these packages (especially with DragonFly's pkg_radd, which
is a wrapper around pkg_add) will get a warning about it being built for a
different version of the operating system.

The warning generates more confusion than anything, in this case, since
pkg_radd is designed to pick out the correct release's packages.

The information is OS_VERSION in BUILD_INFO.
So, OS_VERSION=2.3.2 means not "built for 2.3.2", but "built on 2.3.2".

I don't know how pkg_radd resolve "package XXX built on 2.3.2 works well on 
2.4".

Is there a way to suppress the version warning when installing packages
via pkg_add?  Alternately, is there a way to change the record for what
operating system it was built for?  If there was a way to automate a
change like that, I could run it over our package collection after each
bulk build.

It is probably possible to extract package.tgz, replace OS_VERSION in 
+BUILD_INFO,
re-create package.tgz.

--
"Of course I love NetBSD":-)
OBATA Akio / obache%NetBSD.org@localhost


Home | Main Index | Thread Index | Old Index