Hi,
On Fri, 7 Jun 2019 at 01:49, Ryan Schmidt wrote:
>
> Originally, all-lowercase port names were encouraged, because users often
> specify port names in all lowercase and there were a few bugs in MacPorts
> when the capitalization specified did not match the capitalization used in
> the port.
On Jun 6, 2019, at 21:11, Renee Otten wrote:
> Looking at your comments I must admit I am a little confused, but that is
> probably because I am not understanding some (basic) MacPorts things
> correctly… For example, I didn’t realize (probably never tried) that “port
> info py-sphinx” and "por
On Jun 5, 2019, at 21:36, Karan Sheth wrote:
> 1. The naming convention of Python ports
> For upt to be able to process dependencies correctly and add missing packages
> recursively, it is important to have a consistent naming scheme for ports.
> Currently, that is not completely the case, al
On 06.06.19 04:36, Karan Sheth via macports-dev wrote:
> Community feedback is requested on the following topics:
>
> 1. The naming convention of Python ports
> For upt to be able to process dependencies correctly and add missing
> packages recursively, it is important to have a consistent naming
On 2019-6-6 12:36 , Karan Sheth via macports-dev wrote:
> Community feedback is requested on the following topics:
>
> 1. The naming convention of Python ports
> For upt to be able to process dependencies correctly and add missing
> packages recursively, it is important to have a consistent naming
Dear all,
As you may know, I am working on "Automating Packaging for MacPorts” using
upt (https://framagit.org/upt/upt) as my GSoC project. So I just wanted to
inform the MacPorts community about the current status of the project and
there are a few topics where we would like some input:
Project
