On Jun 28, 2020, at 00:38, Blair Zajac wrote:
> Is this on the wiki?
The guide is where things should be documented. I don't know if all of this is
already there. I'm guessing not, since there seems to have been so much
confusion about it.
I don't spend as much time as maybe I should in
Is this on the wiki?
Also, adding if a port: dependency is changed requires a revision bump would be
good to list for completeness, e.g.
https://github.com/macports/macports-ports/commit/9e9d40fea3f205523d842ff78e5ca8063cffbaf0
.
> On Jun 25, 2020, at 10:00 PM, Ryan Schmidt wrote:
>
> Hi
On Jun 27, 2020, at 23:18, Fred Wright wrote:
> On Fri, 26 Jun 2020, Ryan Schmidt wrote:
>
>> Somehow I missed that we have a shellescape proc. This is very exciting!
>> I've wanted this function for a long time, and I'm just realizing now that
>> it exists and that we've had it for 6
On Fri, 26 Jun 2020, Ryan Schmidt wrote:
Somehow I missed that we have a shellescape proc. This is very exciting!
I've wanted this function for a long time, and I'm just realizing now
that it exists and that we've had it for 6 years.
> On Jun 23, 2020, at 12:48 AM, Ryan Schmidt wrote:
>
> My ports are slightly out of date but I don't see a choking amount of
> dependencies for curl on High Sierra:
>
> $ port rdeps curl
> The following ports are dependencies of curl @7.70.0_0+ssl:
> xz
>lbzip2
>libiconv
>
Awesome, thank you Ryan.
On Sat, Jun 27, 2020 at 1:30 PM Ryan Schmidt
wrote:
>
>
> On Jun 27, 2020, at 11:32, Herby G wrote:
>
> > I have a situation where a particular port is using a distfile of the
> same name from version to version.
> >
> > So there's currently an older version of the
On Jun 27, 2020, at 11:32, Herby G wrote:
> I have a situation where a particular port is using a distfile of the same
> name from version to version.
>
> So there's currently an older version of the port's distfile cached in the
> MacPorts mirrors.
>
> Unfortunately, trying to update the
On 2020-06-27, at 6:27 AM, Daniel J. Luke wrote:
> On Jun 22, 2020, at 11:20 PM, Ryan Schmidt wrote:
>> On Jun 22, 2020, at 14:34, Daniel J. Luke wrote:
>>> We should just have one perl5 port that tracks the current release.
>>
>> You say this every year (or at least often).
>
> I say this
Hello all,
I have a situation where a particular port is using a distfile of the same
name from version to version.
So there's currently an older version of the port's distfile cached in the
MacPorts mirrors.
Unfortunately, trying to update the port is failing since the distfile is
first
A separate macOS install in Parallels or Fusion would be another option, I
guess.
> Am 27.06.2020 um 16:31 schrieb Joshua Root :
>
> On 2020-6-28 00:23 , David Richmond wrote:
>> New here to hacking on MacPorts; please talk to me like I'm dumb. Can
>> anyone point me to a resource (or offer
On 2020-6-28 00:23 , David Richmond wrote:
> New here to hacking on MacPorts; please talk to me like I'm dumb. Can
> anyone point me to a resource (or offer their own thoughts) on setting
> up test environments for ports?
>
> The MacPorts Guide obviously describes setting up a local repository,
>
New here to hacking on MacPorts; please talk to me like I'm dumb. Can
anyone point me to a resource (or offer their own thoughts) on setting up
test environments for ports?
The MacPorts Guide obviously describes setting up a local repository, but
if I am, say, chasing a bug down during build,
On Jun 22, 2020, at 11:20 PM, Ryan Schmidt wrote:
> On Jun 22, 2020, at 14:34, Daniel J. Luke wrote:
>> We should just have one perl5 port that tracks the current release.
>
> You say this every year (or at least often).
I say this every time we run into the set of problems that we would solve
13 matches
Mail list logo
