Re: graphics/opencv2 orphaned. Where from here

[Herbert J. Skuhra]

Rainer Hurling skrev:
> 
> Am 15.04.2017 um 01:04 schrieb Kevin Oberman:
>> Thanks for the work on opencv, but PLEASE put something in UPDATING when
>> you make changes that impact large numbers of ports. I see opencv2 as
>> orphaned, so I can't stay there.
>> 
>> Do I reset the origin of opencv2 to opencv? Or will I need to delete all of
>> them and rebuild everything? Please put information in UPDATING to give us
>> poor users some idea of how to proceed. I really would rathe rnot have to
>> re-install all of those ports if there is no reason.
> 
> As a user of portmaster, all I had to do, was:
> 
> portmaster -o graphics/opencv-core opencv2-core-2.4.13.1_1

Hmm, I had to 'pkg delete opencv2-core' because of

pkg-static: opencv-core-2.4.13.1_1 conflicts with
opencv2-core-2.4.13.1_1 (installs files into the same place).
Problematic file: /usr/local/include/opencv2/core.hpp

and then run 'make install clean' in graphics/opencv-core.

--
Herbert
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: graphics/opencv2 orphaned. Where from here

[Rainer Hurling]

Am 15.04.2017 um 01:04 schrieb Kevin Oberman:
> Thanks for the work on opencv, but PLEASE put something in UPDATING when
> you make changes that impact large numbers of ports. I see opencv2 as
> orphaned, so I can't stay there.
> 
> Do I reset the origin of opencv2 to opencv? Or will I need to delete all of
> them and rebuild everything? Please put information in UPDATING to give us
> poor users some idea of how to proceed. I really would rathe rnot have to
> re-install all of those ports if there is no reason.
> --
> Kevin Oberman, Part time kid herder and retired Network Engineer
> E-mail: rkober...@gmail.com
> PGP Fingerprint: D03FB98AFA78E3B78C1694B318AB39EF1B055683


As a user of portmaster, all I had to do, was:

portmaster -o graphics/opencv-core opencv2-core-2.4.13.1_1
portmaster -o graphics/opencv opencv2-2.4.13.1_6
portmaster -o graphics/py-opencv py27-opencv2-2.4.13.1_1
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"

Re: graphics/opencv2 orphaned. Where from here

[Jan Beich]

Kevin Oberman  writes:

> Thanks for the work on opencv, but PLEASE put something in UPDATING when
> you make changes that impact large numbers of ports. I see opencv2 as
> orphaned, so I can't stay there.

graphics/opencv has only 28 consumers which isn't that "large". I didn't
document the rename in r438490 because:
- no manual/special steps required (for pkg, poudriere and, probably, synth)
- r423216 wasn't documented as well
- partial upgrades were never supported (e.g. /quarterly packages + /head ports)
- PORTREVISION was bumped to help tools that don't (or incompletely) respect 
MOVED

> Do I reset the origin of opencv2 to opencv?

Yes.

> Or will I need to delete all of them and rebuild everything?

No but it'd work as well.

> Please put information in UPDATING to give us poor users some idea of
> how to proceed. I really would rathe rnot have to re-install all of
> those ports if there is no reason.

Does "pkg upgrade" not work? If portmaster is such a special snowflake
that requires multiplying copypasta in UPDATING for every rename that
has > 1 consumer it should be documented it in the Porter's Handbook.
Another issue with portmaster is it makes committers (over)think
skipping PORTREVISION bumps like in 20170411 or 20150919 is safe only to
screw up pkg-upgrade(8) as changed ABI doesn't propagate to consumers.
___
freebsd-ports@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscr...@freebsd.org"