On Sat, Feb 4, 2017 at 9:35 PM, Bachsau wrote:
> Over the years of working with Linux…
I understand, I accept but, if possible, keep in mind that there also are
MacPorts users being no more than (humble) computer users.
This is not a request but only an indication.
Thank all you for all y
https://trac.macports.org/ticket/53490
On Wed, Feb 1, 2017 at 1:42 AM, Ryan Schmidt wrote:
>
>> On Jan 30, 2017, at 20:34, Arno Hautala wrote:
>>
>> I ran 'port diagnose' and I think there's an issue with how it handles
>> symlinks.
>>
>> Specifically:
>>
>>> Checking for file '/opt/local/libex
Am 04.02.2017 um 17:31 schrieb Eneko Gotzon:
Rather, at least in my case,
the
is
s
ue
is
to not having enough time to learn.
I never sat down to learn anything but Python 3 explicitly. Over the
years of working with Linux knowledge came on its own.
smime.p7s
Description: S/MIME Crypt
Could you please review this ticket? I submitted it 8 days ago.
(I already sent this message to the dev list, but got rejected since I'm not
subscribed there, oh well…).
On Thu, Feb 2, 2017 at 8:09 PM, Ryan Schmidt
wrote:
>
> > It depends on the order in your /etc/paths. If I put it first, it is
> first. The advantage of /etc/paths is it is applied even to the graphical
> environment, not just when running a login shell.
>
> Oh, I was thinking of /etc/paths.d
>
>
On Fri, Feb 3, 2017 at 2:09 AM, Ryan Schmidt
wrote:
> There are many nontechnical users…
Yes…
> they don't want to understand how MacPorts or the shell works.
Rather, at least in my case,
the
is
s
ue
is
to not having enough time to learn.
> We should work toward making MacPorts eas
> On Feb 2, 2017, at 12:56 AM, Ryan Schmidt wrote:
>
> On Feb 1, 2017, at 23:42, list_em...@icloud.com wrote:
>>
>> Trying to do selfupdate and had the following problem. Using Version 2.3.4,
>> hoping to upgrade.
>>
>> Is this a permissions problem on /opt? If so, what should the permissions
I too was stuck at 2.3.5 with "no configure script found in vendor/tcl/unix"
On Thu, Feb 2, 2017 at 12:07 PM, Rainer Müller wrote:
> On 2017-02-02 17:40, p...@uvic.ca wrote:
> > I suspect this is almost certainly due
> > to an issue with my own setup since I have seen no other similar
> > probl
I guess I could use a git checkout for everything. I wonder how would that work
with the rsync tarball, as it seems not to be documented in the guide.
Otherwise, I could parse the sources by port directory, list them, rename the
Portfile I want to override and re-index.
On 2 Feb 2017, at 17:24,
> On Feb 1, 2017, at 08:20, Bachsau wrote:
>
> Am 01.02.2017 um 07:38 schrieb Ryan Schmidt:
>> Sorry. Repeated modifications of the profile when the modifications were
>> already there was a bug. It looks like a fix was committed, so hopefully
>> 2.4.1 will not have this bug anymore.
>
> Not
> On Feb 2, 2017, at 12:38, Christopher Stone
> wrote:
>
> On Feb 01, 2017, at 16:20, Ryan Schmidt wrote:
>>> The thing I find most odd about this are all the symlinks.
>>
>> What do you find odd about the symlinks?
> __
>
>
On Feb 02, 2017, at 13:30, Clemens Lang wrote:
> On Thu, Feb 02, 2017 at 12:38:43PM -0600, Christopher Stone wrote:
>> Although I wonder if the error message shouldn't provide the trac link:
>> …
>> It seems to me this would save you some support questions.
>
> Absolutely. Do you have time to sen
On 01/02/2017 21:06, Brandon Allbery wrote:
On Wed, Feb 1, 2017 at 1:42 AM, Ryan Schmidt mailto:ryandes...@macports.org>> wrote:
It looks like the port diagnose code assumes the path is
colon-separated, but your fish shell uses spaces to delimit the
different paths. I guess MacPorts
On Thu, Feb 02, 2017 at 12:38:43PM -0600, Christopher Stone wrote:
> Although I wonder if the error message shouldn't provide the trac
> link:
>
> ---
> Warning: found dylibs in your /usr/local/lib directory. T
14 matches
Mail list logo
