problems installing svg pkg ....
m.seaman at infracaninophile.co.uk
Mon Dec 8 07:15:34 UTC 2014
On 08/12/2014 00:00, Lowell Gilbert wrote:
> "William A. Mahaffey III" <wam at hiwaay.net> writes:
>> Rats !!!! I have been trying to avoid mixing ports & pkg's AMAP
> There is Absolutely No Reason to follow this approach.
> There was, at one time, but that time is now many
> years in the past.
Mixing pkgs and ports is doable now, but...
Yes, with pkg(8) and the new pkg repositories with weekly package
updates it is much more feasible to mix standard pkgs and pkgs you
compile yourself. However you need to understand that -
- Standard packages have the default options settings. This means
that where there are alternate dependency choices then the default
dependencies are what you're going to get from the standard pkgs.
- There's a delay of 4--5 days while the standard pkgs are compiled,
and they are on a weekly cycle, so your local ports tree may well
be up to 10 days ahead of what's available from the pkg repos.
The first of these is a structural problem in the ports, in that package
dependencies are 'baked in' as being on exact versions of the upstream
pkg dependencies at compile time. This contrasts with the flexibility
available before compiling. In practice this means that substituting
your own-built pkgs works best for leaf ports.
The second is usually pretty harmless and would tend to only affect a
few ports most of the time. However, on occasion there will be
wide-scale changes in the ports which have a more significant impact.
The recent changes from getopts to getopts-runtime and to the way perl
ports are installed are cases in point. You can work round it by always
checking out the ports tree using the revision that was current on the
previous Wednesday night.
Dr Matthew J Seaman MA, D.Phil.
JID: matthew at infracaninophile.co.uk
-------------- next part --------------
A non-text attachment was scrubbed...
Size: 971 bytes
Desc: OpenPGP digital signature
More information about the freebsd-questions