Re: New port gitsome
On Wed, Mar 01, 2017 at 08:46:38PM -0300, Danilo G. Baio (dbaio) wrote: > > Gitsome submitted in PR 217484[1] and each dependency in a separate PR. > > Thank you Olivier, this way that you said worked better, other > changes/problems showed up when I was testing each individual port with > poudriete testport. > > [1] - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217484 > > Regards. > -- > Danilo G. Baio (dbaio) > Hi. It's almost done: https://bugs.freebsd.org/bugzilla/showdependencytree.cgi?id=217484&hide_resolved=0 I submitted an update to the main PR(it was released 0.7.0 version of gitsome) and taking a hook on it, I need some help with these PR's: 217468,217482,217480 (Maintainer timeout 4 weeks) 217469 (Maintainer reset) And thank you all that helped so far. Regards. -- Danilo G. Baio (dbaio) signature.asc Description: PGP signature
Re: New port gitsome
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)" 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
Re: New port gitsome
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)" 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 signature.asc Description: OpenPGP digital signature
Re: New port gitsome
On Mon, Feb 27, 2017 at 07:33:43AM -0300, Danilo G. Baio (dbaio) wrote: > 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)" 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. > > I will wait a little longer and if no one agrees with this I will submit one > PR for each new py3- port (17). > > Thank you again. Gitsome submitted in PR 217484[1] and each dependency in a separate PR. Thank you Olivier, this way that you said worked better, other changes/problems showed up when I was testing each individual port with poudriete testport. [1] - https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=217484 Regards. -- Danilo G. Baio (dbaio) signature.asc Description: PGP signature
Re: New port gitsome
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)" 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. I will wait a little longer and if no one agrees with this I will submit one PR for each new py3- port (17). Thank you again. Regards. -- Danilo G. Baio (dbaio) signature.asc Description: PGP signature
Re: New port gitsome
On Sat, 25 Feb 2017 16:48:17 -0300 "Danilo G. Baio (dbaio)" 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 ___ 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: New port gitsome
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? Regards. -- Danilo G. Baio (dbaio) signature.asc Description: PGP signature
Re: New port gitsome
On Sat, 25 Feb 2017 15:13:52 -0300 "Danilo G. Baio (dbaio)" wrote: > On Wed, Feb 22, 2017 at 08:24:54PM -0300, Danilo G. Baio (dbaio) wrote: > > On Wed, Feb 22, 2017 at 11:00:55PM +, Ben Woods wrote: > > > On Wed, 22 Feb 2017 at 6:52 pm, Danilo G. Baio (dbaio) > > > wrote: > > > > > > > Hi. > > > > > > > > I am working on a new port for gitsome[1] which depends on > > > > python:3.4-3.5. > > [snip] > > > > Hi Danilo, > > > > > > Apologies in the delay in getting back to you. > > > > > > Yes, at the moment that is the only way to get a port working which > > > depends > > > on multiple python3 ports. > > > > > > Bapt is working on bringing "flavours" to the ports tree, which will allow > > > each python port to be built multiple times with python2 and python3, > > > therefore satisfying your dependencies. > > > > > > However, it is probably not have in the next week or so, so you should go > > > ahead and make the py3- versions of those ports. It is easy to find and > > > revert them once flavours exist anyway :) > > > > > > Before we commit all of those new py3- ports, please make sure you have > > > tested that it all successfully builds to provide a working gitsome we > > > don't want to commit them and find out they were not needed after all :) > > > > > > Regards, > > > Ben > > > -- > > > > > > -- > > > From: Benjamin Woods > > > woods...@gmail.com > > > > Hi Ben. > > > > Thank you for your answer. > > > > Ok then, I will work on this and submit it to bugzilla and also I will test > > it > > on poudriere for making sure it's all needed. > > > Hi Ben and others. > > One last question... What is the recommendation here? > > Thinking about creating two PR's. > > One PR for gitsome and another PR for all dependencies together, CC'ing all > involved. > > The default changes in all ports are just for preparing them to be a master > port. > > Exceptions: > > devel/py-ply/Makefile (also take maintainer'ship) > textproc/py-pystemmer (also take maintainer'ship) > textproc/py-snowballstemmer (also use options helpers) > > Tree of dependencies (new ports needed): > > -misc/py-gitsome > > [1] textproc/py3-numpydoc > [2] textproc/py3-sphinx > [3] textproc/py3-docutils > [3] devel/py3-six * > [3] textproc/py3-sphinx_rtd_theme > [3] textproc/py3-alabaster > [3] textproc/py3-snowballstemmer > [4]textproc/py3-pystemmer > [3] graphics/py3-imagesize > [1] devel/py3-ply > [1] devel/py3-prompt_toolkit > [2] devel/py3-wcwidth > [1] devel/py3-colorama > [1] textproc/py3-pygments > [1] textproc/py3-feedparser > [1] devel/py3-docopt > [1] net/py3-uritemplate > > * Needed also on devel/py3-prompt_toolkit. > > They are all direct dependencies to run or build another port. > > I am setting me as maintainer of these new ports to not let "trouble" for > others. > Remembering that soon all these ports will be un-necessary. 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"). > > Patches are here (feedbacks are welcome): > http://dbaio.bs2cloud.com.br/FreeBSD/misc_py-gitsome.patch > http://dbaio.bs2cloud.com.br/FreeBSD/misc_py-gitsome__py3-dependencies.patch > > For whom is interested in the build logs, more info here: > http://dbaio.bs2cloud.com.br/FreeBSD/misc_py-gitsome__build_log.txt > > Screenshot in a clean instance from DigitalOcean: > http://dbaio.bs2cloud.com.br/FreeBSD/misc_py-gitsome__avatar_scrot.png > > Regards. > > -- > Danilo G. Baio (dbaio) Regards, -- olivier ___ 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: New port gitsome
On Wed, Feb 22, 2017 at 08:24:54PM -0300, Danilo G. Baio (dbaio) wrote: > On Wed, Feb 22, 2017 at 11:00:55PM +, Ben Woods wrote: > > On Wed, 22 Feb 2017 at 6:52 pm, Danilo G. Baio (dbaio) > > wrote: > > > > > Hi. > > > > > > I am working on a new port for gitsome[1] which depends on python:3.4-3.5. [snip] > > Hi Danilo, > > > > Apologies in the delay in getting back to you. > > > > Yes, at the moment that is the only way to get a port working which depends > > on multiple python3 ports. > > > > Bapt is working on bringing "flavours" to the ports tree, which will allow > > each python port to be built multiple times with python2 and python3, > > therefore satisfying your dependencies. > > > > However, it is probably not have in the next week or so, so you should go > > ahead and make the py3- versions of those ports. It is easy to find and > > revert them once flavours exist anyway :) > > > > Before we commit all of those new py3- ports, please make sure you have > > tested that it all successfully builds to provide a working gitsome we > > don't want to commit them and find out they were not needed after all :) > > > > Regards, > > Ben > > -- > > > > -- > > From: Benjamin Woods > > woods...@gmail.com > > Hi Ben. > > Thank you for your answer. > > Ok then, I will work on this and submit it to bugzilla and also I will test it > on poudriere for making sure it's all needed. Hi Ben and others. One last question... What is the recommendation here? Thinking about creating two PR's. One PR for gitsome and another PR for all dependencies together, CC'ing all involved. The default changes in all ports are just for preparing them to be a master port. Exceptions: devel/py-ply/Makefile (also take maintainer'ship) textproc/py-pystemmer (also take maintainer'ship) textproc/py-snowballstemmer (also use options helpers) Tree of dependencies (new ports needed): -misc/py-gitsome [1] textproc/py3-numpydoc [2] textproc/py3-sphinx [3] textproc/py3-docutils [3] devel/py3-six * [3] textproc/py3-sphinx_rtd_theme [3] textproc/py3-alabaster [3] textproc/py3-snowballstemmer [4]textproc/py3-pystemmer [3] graphics/py3-imagesize [1] devel/py3-ply [1] devel/py3-prompt_toolkit [2] devel/py3-wcwidth [1] devel/py3-colorama [1] textproc/py3-pygments [1] textproc/py3-feedparser [1] devel/py3-docopt [1] net/py3-uritemplate * Needed also on devel/py3-prompt_toolkit. They are all direct dependencies to run or build another port. I am setting me as maintainer of these new ports to not let "trouble" for others. Remembering that soon all these ports will be un-necessary. Patches are here (feedbacks are welcome): http://dbaio.bs2cloud.com.br/FreeBSD/misc_py-gitsome.patch http://dbaio.bs2cloud.com.br/FreeBSD/misc_py-gitsome__py3-dependencies.patch For whom is interested in the build logs, more info here: http://dbaio.bs2cloud.com.br/FreeBSD/misc_py-gitsome__build_log.txt Screenshot in a clean instance from DigitalOcean: http://dbaio.bs2cloud.com.br/FreeBSD/misc_py-gitsome__avatar_scrot.png Regards. -- Danilo G. Baio (dbaio) signature.asc Description: PGP signature
Re: New port gitsome
On Wed, Feb 22, 2017 at 11:00:55PM +, Ben Woods wrote: > On Wed, 22 Feb 2017 at 6:52 pm, Danilo G. Baio (dbaio) > wrote: > > > Hi. > > > > I am working on a new port for gitsome[1] which depends on python:3.4-3.5. > > > > But it will fail on FreeBSD poudriere (building infrastructure) because > > some > > of its dependencies (at least 17) won't be build with python 3. > > > > What is the advice here ? Submit for each dependency [2] a py3-\* slave > > port ? > > > > Regards. > > > > [1] - http://dbaio.bs2cloud.com.br/FreeBSD/misc_py-gitsome.patch > > > > [2] > > textproc/py-pygments > > textproc/py-pystemmer > > textproc/py-alabaster > > textproc/py-snowballstemmer > > devel/py-six > > textproc/py-docutils > > devel/py-wcwidth > > graphics/py-imagesize > > textproc/py-sphinx_rtd_theme > > devel/py-colorama > > textproc/py-feedparser > > devel/py-docopt > > devel/py-ply > > textproc/py-sphinx > > net/py-uritemplate > > devel/py-prompt_toolkit > > textproc/py-numpydoc > > > > -- > > Danilo G. Baio (dbaio) > > > Hi Danilo, > > Apologies in the delay in getting back to you. > > Yes, at the moment that is the only way to get a port working which depends > on multiple python3 ports. > > Bapt is working on bringing "flavours" to the ports tree, which will allow > each python port to be built multiple times with python2 and python3, > therefore satisfying your dependencies. > > However, it is probably not have in the next week or so, so you should go > ahead and make the py3- versions of those ports. It is easy to find and > revert them once flavours exist anyway :) > > Before we commit all of those new py3- ports, please make sure you have > tested that it all successfully builds to provide a working gitsome we > don't want to commit them and find out they were not needed after all :) > > Regards, > Ben > -- > > -- > From: Benjamin Woods > woods...@gmail.com Hi Ben. Thank you for your answer. Ok then, I will work on this and submit it to bugzilla and also I will test it on poudriere for making sure it's all needed. Best regards. -- Danilo G. Baio (dbaio) signature.asc Description: PGP signature
Re: New port gitsome
On Wed, 22 Feb 2017 at 6:52 pm, Danilo G. Baio (dbaio) wrote: > Hi. > > I am working on a new port for gitsome[1] which depends on python:3.4-3.5. > > But it will fail on FreeBSD poudriere (building infrastructure) because > some > of its dependencies (at least 17) won't be build with python 3. > > What is the advice here ? Submit for each dependency [2] a py3-\* slave > port ? > > Regards. > > [1] - http://dbaio.bs2cloud.com.br/FreeBSD/misc_py-gitsome.patch > > [2] > textproc/py-pygments > textproc/py-pystemmer > textproc/py-alabaster > textproc/py-snowballstemmer > devel/py-six > textproc/py-docutils > devel/py-wcwidth > graphics/py-imagesize > textproc/py-sphinx_rtd_theme > devel/py-colorama > textproc/py-feedparser > devel/py-docopt > devel/py-ply > textproc/py-sphinx > net/py-uritemplate > devel/py-prompt_toolkit > textproc/py-numpydoc > > -- > Danilo G. Baio (dbaio) > Hi Danilo, Apologies in the delay in getting back to you. Yes, at the moment that is the only way to get a port working which depends on multiple python3 ports. Bapt is working on bringing "flavours" to the ports tree, which will allow each python port to be built multiple times with python2 and python3, therefore satisfying your dependencies. However, it is probably not have in the next week or so, so you should go ahead and make the py3- versions of those ports. It is easy to find and revert them once flavours exist anyway :) Before we commit all of those new py3- ports, please make sure you have tested that it all successfully builds to provide a working gitsome we don't want to commit them and find out they were not needed after all :) Regards, Ben -- -- From: Benjamin Woods woods...@gmail.com ___ 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"
