On Thu, Mar 02, 2017 at 08:45:57AM +0100, Mathieu Arnold wrote: > Le 27/02/2017 à 11:33, Danilo G. Baio (dbaio) a écrit : > > On Sat, Feb 25, 2017 at 09:42:38PM +0100, Olivier Duchateau wrote: > >> On Sat, 25 Feb 2017 16:48:17 -0300 > >> "Danilo G. Baio (dbaio)" <db...@bsd.com.br> wrote: > >> > >>> On Sat, Feb 25, 2017 at 07:48:05PM +0100, Olivier Duchateau wrote: > >>>> For py3-* ports, you can look at how audio/py-mutagen and > >>>> audio/py3-mutagen are build. > >>>> > >>>> I don't think, you need to become maintainer of these ports (it's just > >>>> "copy of"). > >>>> > >>> Hi Olivier. > >>> > >>> I've withdrawn maintainer entry on the new py3-* ports. Patch updated. > >>> > >>> And is ok, just one PR for all py3-* ports? > >> This question depends of commiter. > >> > >> Personally I prefer new patch for each new port. Besides Bugzilla is > >> clever, you can add an ordered list of dependencies for a given port. > >> > >>> Regards. > >>> -- > >>> Danilo G. Baio (dbaio) > >> > >> -- > >> olivier > > > > But like all py3-* new ports are just a 'copy of' and serves for the same > > purpose I thought that one patch and one commit will work. > > py3-* ports should never be copies, they should be slave ports of the > py-* versions. > > > -- > Mathieu Arnold > >
Right, they are all slaves. The reference of 'copy of' is because basically is changed only `USES`. Regards. -- Danilo G. Baio (dbaio)
signature.asc
Description: PGP signature
