On Sat, Mar 21 2020, Bjorn Ketelaars <b...@openbsd.org> wrote: > On Sat 21/03/2020 16:12, Remi Pointel wrote: >> On 2020-03-10 10:19, Jeremie Courreges-Anglas wrote: >> > On Mon, Mar 09 2020, Paco Esteban <p...@e1e0.net> wrote: >> > > Hi Remi, >> > > >> > > On Sun, 08 Mar 2020, Remi Pointel wrote: >> > > >> > > > Hi, >> > > > >> > > > these are the diff to update filebytes and ropper to latest releases. >> > > > >> > > > Ok? >> > >> > LGTM and appears to work fine in my tests on amd64, ok jca@ >> > >> > > ropper has no consumers and filebytes only has ropper. I gess those are >> > > perfect candidates to go py3 only, don't you think ? >> > >> > It appears so indeed. >> > >> >> >> Hi, >> >> these are the diff to use Python 3 only. >> >> Ok? > > Is there a reason that you are not using @conflict markers in PLIST?
Same question. Assuming there is no reason to avoid the conflict marker, please add @conflict py-pkgname-* to the PLIST of both ports, and don't forget to drop "SUBDIR += py-pkgname" from ../Makefile. With this, ok jca@ for the python3-only bits, I did not test the ropper update (you probably can get enough coverage without my simple tests). -- jca | PGP : 0x1524E7EE / 5135 92C1 AD36 5293 2BDF DDCC 0DFA 74AE 1524 E7EE
