On 2015-11-09 18:18, Artur Szostak wrote:
> OK, I got confused because Rainer started off with "Yes this is
> supported...", sorry.
> I conclude that what I am asking for is not supported.
Apparently I misunderstood your intention. Sorry for the confusion.
However, note that even if a port is not
On 2015-11-09 21:01, Mojca Miklavec wrote:
> Does anyone know who owns
> https://github.com/MacPorts
> ?
I would be interested to know that as well. I actually found a way to
send them a message last week. Now we can just wait for them to get back
to us.
Rainer
___
Does anyone know who owns
https://github.com/MacPorts
?
Thank you,
Mojca
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Make sure you note on the ticket if/when upstream accepts your patch (or if it
accepts a modified version) - as it will make it much more likely that a
theoretical openssh maintainer (or someone who is interested with commit
access) will include it if it's accepted upstream.
> On Nov 4, 2015, a
Thanks. That makes things much simpler.
From: Joshua Root [j...@macports.org]
Sent: 09 November 2015 20:02
To: Artur Szostak; MacPorts Development
Subject: Re: Getting proper dependency order using port command
On 2015-11-10 04:35 , Artur Szostak wrote:
>
On 2015-11-10 04:35 , Artur Szostak wrote:
> Hi,
>
> I do not see the documentation indicating the options --follow-dependents or
> --follow-dependencies for the "port deactivate" command. Therefore I need to
> run the deactivate command on one port at a time in the proper order.
> How can I get
I think I might have found a solution if someone can confirm the following:
Does the "port rdeps" command print in pre-order depth first?
If so then I can just reverse the order of the printed list.
From: macports-dev-boun...@lists.macosforge.org
[macports
Hi,
I do not see the documentation indicating the options --follow-dependents or
--follow-dependencies for the "port deactivate" command. Therefore I need to
run the deactivate command on one port at a time in the proper order.
How can I get the post-order depth first search of the dependency tr
OK, I got confused because Rainer started off with "Yes this is supported...",
sorry.
I conclude that what I am asking for is not supported.
Thanks.
From: Brandon Allbery [allber...@gmail.com]
Sent: 09 November 2015 18:16
To: Artur Szostak
Cc: Rainer Müller; macpo
On Mon, Nov 9, 2015 at 12:18 PM, Artur Szostak
wrote:
> OK, I got confused because Rainer started off with "Yes this is
> supported...", sorry.
> I conclude that what I am asking for is not supported.
>
It's not supported the way you want, no. I suspect a considerable overhaul
of PortIndex handl
On Mon, Nov 9, 2015 at 12:10 PM, Artur Szostak
wrote:
> > considered by MacPorts. The first ports tree that contains a port by
> > that name in the order listed in sources.conf will be used. All other
> > Portfiles in ports trees listed below that are not considered at all for
> > any port action
>> Is MacPorts supposed to work correctly if multiple repositories are added to
>> the /opt/local/etc/macports/sources.conf file, each with a different version
>> of the Portfile, but with the same port name?
>> In such a scenario with multiple versions, I notice that things like the
>> followin
On 2015-11-09 17:08, Artur Szostak wrote:
> Is MacPorts supposed to work correctly if multiple repositories are added to
> the /opt/local/etc/macports/sources.conf file, each with a different version
> of the Portfile, but with the same port name?
> In such a scenario with multiple versions, I no
On 2015-11-10 03:08 , Artur Szostak wrote:
> Hi,
>
> Is MacPorts supposed to work correctly if multiple repositories are added to
> the /opt/local/etc/macports/sources.conf file, each with a different version
> of the Portfile, but with the same port name?
> In such a scenario with multiple vers
Hi,
Is MacPorts supposed to work correctly if multiple repositories are added to
the /opt/local/etc/macports/sources.conf file, each with a different version of
the Portfile, but with the same port name?
In such a scenario with multiple versions, I notice that things like the
following do not a
On Monday November 09 2015 09:46:57 Brandon Allbery wrote:
> Right; the point was more that you'll probably need to adjust
> /proc/sys/kernel/core_pattern to stop it from intercepting core dumps. (Red
> Hat/Fedora do the same thing, only it's called "abrt".)
Heh. I think I prefer the occasional u
On Mon, Nov 9, 2015 at 9:42 AM, René J.V. wrote:
> Part of the tell-tale signs of a crash in a non-KDE application is an
> apport notification. It's really focused on Ubuntu packages though: rather
> useless for self-build applications that aren't installed through an
> official package.
> (I do
On Monday November 09 2015 09:10:04 Brandon Allbery wrote:
\
>https://wiki.ubuntu.com/Apport
Ah, yes, that thing (thanks, I guess) :)
Part of the tell-tale signs of a crash in a non-KDE application is an apport
notification. It's really focused on Ubuntu packages though: rather useless for
se
On Mon, Nov 9, 2015 at 6:03 AM, René J.V. wrote:
> I guess I'll have to figure out how to get actual core dumps on that linux
> rig (Kubuntu 14.04). I seem to recall I already set the relevant ulimit.
https://wiki.ubuntu.com/Apport
--
brandon s allbery kf8nh sine
On Monday November 09 2015 11:39:27 Rainer Müller wrote:
> Exit code 139 is usually how a shell tells you the command died with
> signal 11, which is SIGSEGV (Segmentation Fault). The process made an
> invalid memory access and is terminated abruptly.
Except that I'm not getting the other message
On 2015-11-09 10:34, René J.V. Bertin wrote:
> However, port now exits with code 139 each time it terminates with
> the rev-upgrade phase, and there is no debug output whatsoever to
> determine why.
Exit code 139 is usually how a shell tells you the command died with
signal 11, which is SIGSEGV (S
Hi,
Ok, so I've been playing with MacPorts on Linux again, and I know that's not
supported. Yet, more things (ports) work than I expected, and as I argued
elsewhere, I'm getting some use out of it (even -or maybe, especially- with a
relaxed reproducible-builds approach that allows ports to use
22 matches
Mail list logo
