Strange that something as important as a package management system doesnt have
up-to-date/accurate documentation. For example, this is the first item in
google search for "FreeBSD pkg"
https://www.freebsd.org/doc/handbook/pkgng-intro.html (useful for rudimentary
use. This is official
:
On 07/11/20 20:51, Yuet-nan Wong via freebsd-ports wrote:
> Is there a particular reason why?
https://en.wikipedia.org/wiki/Unix_time
--
Guido Falsi
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-po
Is there a particular reason why?
Also is there a place where pkg is documented? A frontlog of changes would be
very helpful.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any
Thanks.
jq was quite helpful but the syntax convoluted. Fortunately with thispkg info
-R -F xyzzy-1.0.txz (and some while reads)
and/usr/local/sbin/pkg-static -d add --no-scripts -f I was able to achieve all
my short term goals.
I did not know that I could examine the package content
Is there a command, or short script that enables the +MANIFEST to be examined.
There are cases where we want to review what the scripts section of the
+MANIFEST contains. In particular the post-install script.
What we're trying to achieve is something like
pkg view scripts post-install -f
Can someone advise how devel/binutils should be used. I notice a lot of
spinoffs from devel/binutils. Should I use one of the spinoffs. I always build
ports with devel/binutils but building ports on i386 FreeBSD 11.2 come back
with message
/usr/local/bin/ld:
Are FreeBSD ports supposed to change version numbers when a change is made?
Issue is reproducibility is void when packages have changed like suricata or
the many changes to binutils. Some removing package content but version not
changed. Need to diff Makefile is inefficient.
