Re: svn commit: r531949 - in head/devel: . libuInputPlus
On Sat, Apr 18, 2020 at 05:49:43PM +1000, Kubilay Kocak wrote: > On 18/04/2020 5:10 pm, Alexey Dokuchaev wrote: > > On Sat, Apr 18, 2020 at 06:28:06AM +, Baptiste Daroussin wrote: > > > I never understood why portname should be lowercase if upstream considers > > > it should not, there are precedent of mixed case (actually respecting > > > upstream will). > > > > For the same reasons we don't have `www/Firefox', `databases/PostgreSQL', > > etc. It does not look unixish. There are few special cases when it is > > indeed desirable to use mixed cased names, e.g. CPAN packages, Python > > modules, those things with established naming convention of their own, when > > we bring lots of them to our ports and want to stay more or less consistent > > with popular GNU/Linux distributions, but those are isolated groups. > > The Python example is in fact actually an example for the opposite. Well, what I was saying there is that Python ports are distinctive, large group of ports that may prefer to follow some specific naming convention. Perhaps I should've just mentioned CPAN. > The reason we lower-case as a policy in Python is to reduce human, > contributor, maintainer, committer error by reducing/removing the impedance > mismatch between the case insensitivity upstream vs case sensitivity in > ports. Awesome, so you guys also follow the default sane convention. That's good. ./danfe ___ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
Re: svn commit: r463374 - head/security/nyx
On 3/2/18 6:40 PM, Yuri wrote: > If the port can only be used as an app, as opposed to library, multiple > flavors aren't needed. All users care about is an executable. It doesn't > matter what python version is used. That's what sane^Wyou and I would think. :-) On Fri, Mar 02, 2018 at 06:57:51PM +1100, Kubilay Kocak wrote: > 2) The 'app vs library' distinction is not sound here. It wasn't sound > for python package prefixing in the past either. It was always sound and meaningful, but FreeBSD Python cabal had decided otherwise (and adopted that stupid "prefix everything with py-" rule which is counterintuitive and makes looking for programs harder). But oh well, we've argued over this years ago Kubilay. ./danfe ___ freebsd-python@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to "freebsd-python-unsubscr...@freebsd.org"
New python port maintainership question
Hi there, Simple question: I am thinking about adding some Python modules to our Collection; can I set MAINTAINER to python@ or I must set it to myself? Thanks. ./danfe ___ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to freebsd-python-unsubscr...@freebsd.org
Re: New python port maintainership question
On Sun, Sep 19, 2010 at 11:29:52PM +0800, Li-Wen Hsu wrote: Currently python@ maintains the lang/python* ports and some key ports. And it is not recommended add a new port setting MAINTAINER to python@ unless this port is really needed to maintained by the python team. Fair enough; I was thinking similar and that's why I asked before taking any action. What are the modules you want to add? Simple py-crcmod module that I needed for crc16 calculations; shar for review is available here: http://freebsd.nsu.ru/crcmod.shar ./danfe ___ freebsd-python@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-python To unsubscribe, send any mail to freebsd-python-unsubscr...@freebsd.org
