On 8/07/2020 5:23 pm, Baptiste Daroussin wrote:
> On Wed, Jul 08, 2020 at 04:32:34PM +1000, Dewayne Geraghty wrote:
>> Is there a more convenient method to examine a package's scripts than
>> unpacking the manifest file and
>> # cat +MANIFEST | jq -rM '.scripts'
>> ? As I'd like to know what
On Wed, Jul 08, 2020 at 04:32:34PM +1000, Dewayne Geraghty wrote:
> Is there a more convenient method to examine a package's scripts than
> unpacking the manifest file and
> # cat +MANIFEST | jq -rM '.scripts'
> ? As I'd like to know what changes will, or have been applied.
pkg info --raw-format
On 8/07/2020 4:52 pm, Dave Horsfall wrote:
> On Wed, 8 Jul 2020, Dewayne Geraghty wrote:
>
>> # cat +MANIFEST | jq -rM '.scripts'
>
> Sorry, but this always pushes one of my buttons. When using "cat file |
> proc"
> what's wrong with "proc < file"?
>
> -- Dave
Almost answered the question.
On Wed, 8 Jul 2020, Dewayne Geraghty wrote:
# cat +MANIFEST | jq -rM '.scripts'
Sorry, but this always pushes one of my buttons. When using "cat file | proc"
what's wrong with "proc < file"?
-- Dave
___
freebsd-ports@freebsd.org mailing list
Is there a more convenient method to examine a package's scripts than
unpacking the manifest file and
# cat +MANIFEST | jq -rM '.scripts'
? As I'd like to know what changes will, or have been applied.
For example to review the dependencies of a file
# pkg info -d -F