On 14.01.20 03:12, Ryan Schmidt wrote:
On Jan 13, 2020, at 03:52, joerg van den hoff wrote:
hi there,
not that long ago I asked for updating the ksh package and ryan thankfully did that and
interacted a bit with the ast/ksh project ("ksh2020") at github in the process.
in the intervenin
Hi,
I'm trying to get macports to use a local (file://) repository for a
macports installed in a non-standard prefix (in this case, a project local
macports, ie per user, per project) with a mixture of private and public
port files. I want to be able to build from source the first time, then use
a
> Are you certain?
“Often wrong, never in doubt.”
Yes, I am certain:
> sudo launchctl unload -w
> /System/Library/LaunchDaemons/com.apple.postfix.master.plist
>
> /System/Library/LaunchDaemons/com.apple.postfix.master.plist: Operation not
> permitted while System Integrity Protection is enga
> "reset" is not a git command I ever run in the normal course of my
> contributions to MacPorts
Practically, the most efficient way to fix conflicts or really any git local
error is to save work outside git, do a `git reset --hard upstream/master`, and
copy the work back.
This is also true fo
On Tue, Jan 14, 2020 at 09:04:41AM -0500, Steven Smith wrote:
> > "reset" is not a git command I ever run in the normal course of my
> > contributions to MacPorts
>
> Practically, the most efficient way to fix conflicts or really any
> git local error is to save work outside git, do a `git reset
On Jan 14, 2020, at 03:35, joerg van den hoff wrote:
> 1.
> would you consider to alter the naming/description of the current `ksh'
> package to reflect that it is actually _not_ ksh93 any more (in terms of
> stability, performance etc)?
I already did change the name of the port from ksh93 to
On Jan 14, 2020, at 03:52, Raphael Cohn wrote:
> I'm trying to get macports to use a local (file://) repository for a macports
> installed in a non-standard prefix (in this case, a project local macports,
> ie per user, per project) with a mixture of private and public port files. I
> want t
What I'd like to do is run my own local archive in my own machine without
running a webserver.
I'd like to compile my ports from source and install them. I'd like to
uninstall them. The next time I install I'd like to use the previously
built results. The archives created in var/macports/software
On Jan 14, 2020, at 14:43, Raphael Cohn wrote:
> What I'd like to do is run my own local archive in my own machine without
> running a webserver.
>
> I'd like to compile my ports from source and install them. I'd like to
> uninstall them. The next time I install I'd like to use the previousl
When I uninstall the ports the archives are still present in
var/macports/software.
An overlay is an archive that can be extracted over an existing filesystem.
Regardless, how do I go about creating a local file repo of binary ports?
On Tue, 14 Jan 2020, 21:02 Ryan Schmidt, wrote:
>
>
> On Ja
On Jan 14, 2020, at 15:42, Raphael Cohn wrote:
> When I uninstall the ports the archives are still present in
> var/macports/software.
Hmm. You've modified MacPorts base so that it does not delete the archives upon
uninstallation?
> An overlay is an archive that can be extracted over an ex
11 matches
Mail list logo
