On Fri, Mar 11, 2016 at 04:10:56PM +0300, Slawa Olhovchenkov wrote: > On Fri, Mar 11, 2016 at 01:05:11PM +0100, Baptiste Daroussin wrote: > > > On Tue, Mar 08, 2016 at 05:35:59PM +0000, David Chisnall wrote: > > > On 8 Mar 2016, at 15:14, Slawa Olhovchenkov <s...@zxy.spb.ru> wrote: > > > > > > > > > > In terms of comparing packages, if you’re doing that visually then you > > > are likely to have problems anyway, unless your eyes and brain work far > > > better than most humans. We can make that much easier by providing libxo > > > output in pkg and allowing you to have a simple jq script that tells you > > > what the differences are. > > > > > pkg can already expose the entire content of a package in json or ucl via: > > $ pkg info --raw --raw-format [json|json-conpact|yaml|ucl] name > > Exposing the entire content of a package is not a root of cause. > Question in comapring of two different setup with different behaviour > and search cause of difference. > > Case of only a few monolitic packages is essentiality simple then case > of 1000 combined packages. pkg info -a on one diff with pkg info -a on the other for the full content: pkg info -a --raw on both end and diff them.
That should cover your case, no? Bapt
Description: PGP signature