why a persistent GCC GCC49 conflict?

[Matthew Seaman]

On 2017/01/20 15:23, Dimitry Andric wrote:
> I don't know why pkg can't see this as a direct replacement.  Perhaps
> pkg does not have support for such metadata.
> 

If there's an entry in ${PORTSDIR}/MOVED saying that lang/gcc49 was
changed to lang/gcc then pkg(8) should replace lang/gcc49 with lang/gcc
for you without trashing anything that depended on lang/gcc49

In more general terms, this is an effect of the strict package+version
dependencies that get baked into packages when they are created.  This
needs a mechanism in pkg(8) for specifying alternate dependencies and
allowed ranges of versions.  Plus tooling in ports to add all this info
to port makefiles and have it included in the generated packages.

	Cheers,

	Matthew


-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 972 bytes
Desc: OpenPGP digital signature
URL: <http://lists.freebsd.org/pipermail/freebsd-ports/attachments/20170120/e141787b/attachment.sig>