There should be a requirement to check if a port exists before committing something right into the master

Otherwise we get this: https://github.com/macports/macports-ports/commit/6e2c1e19a4ffce5d59a9cdf8147022ad176dffed While LimeChat has existed for 4 years in MacPorts: https://github.com/macports/macports-ports/commits/8c30b0e9fd88d94c115b38c92809b909c4eac9aa/aqua/LimeChat/Portfile And now two co

Re: There should be a requirement to check if a port exists before committing something right into the master

On 31/5/2024 21:22, Sergio Had wrote: Otherwise we get this: https://github.com/macports/macports-ports/commit/6e2c1e19a4ffce5d59a9cdf8147022ad176dffed While LimeChat has existed for 4 years in MacPorts

Building MacPorts - why not activate Tcl 64bit support?

Hi, Looking through MacPorts configure.ac and the Tcl configure script I noticed that the latter requires explicit activation of 64bit support and that the former doesn't do that. Is that simply to keep support for building on 32bit systems simple or is there another reason? I am not familiar

Re: There should be a requirement to check if a port exists before committing something right into the master

Is it a guarantee that the PortIndex is available to `port` everytime `port lint` is run? If so, would it be possible for us to use the port index to verify that one and only one port exists for the current port name? On Fri, May 31, 2024 at 8:35 AM Joshua Root wrote: > On 31/5/2024 21:22, Sergi

Re: Building MacPorts - why not activate Tcl 64bit support?

On Fri, 31 May 2024 18:06:33 +0100, "René J.V." Bertin wrote: > > Is that simply to keep support for building on 32bit systems simple or is > there another reason? I am not familiar enough with Tcl to know if there's > any advantage to activating 64bit support ... but that's what MS once though

Re: There should be a requirement to check if a port exists before committing something right into the master

On Fri, 31 May 2024 18:45:53 +0100, Herby G wrote: > > Is it a guarantee that the PortIndex is available to `port` everytime `port > lint` is run? If so, would it be possible for us to use the port index to > verify that one and only one port exists for the current port name? > Another option is

Re: There should be a requirement to check if a port exists before committing something right into the master

No, there's no guarantee that a PortIndex exists; you can run port commands on the 'current' pseudoport, or with -D, or directly on a porturl. The PortIndex itself is indexed on the port name normalised to lower case, so it is not straightforward to detect this situation even with an index. A w

Re: There should be a requirement to check if a port exists before committing something right into the master

I remembered I wrote a script years ago to detect this very situation. Attaching in case it's of use to anyone. There are currently no other duplicate ports in macports-ports, BTW. :) - Josh On 1/6/2024 07:11, Joshua Root wrote: No, there's no guarantee that a PortIndex exists; you can run por

Port sync is broken: Error: Failed to verify signature for ports tree!

sent 78567 bytes received 194729 bytes 20244.15 bytes/sec total size is 125495808 speedup is 459.19 Error: Failed to verify signature for ports tree! port sync failed: Synchronization of 1 source failed