2014-02-28 11:09 GMT-05:00 Clemens Lang :
> > - when updating an existing port, is it recommended to copy in your own
> depot
> > (own user) or work on the existing one (as root)? in the first case, it
> > seems that not all action are prioritizing repositories in the same order
> > (install and b
On Feb 28, 2014, at 17:16, Tony S. Wu wrote:
> Is there a port for MySQL Server that is built with SSL support?
Select the +openssl variant of whatever mysql port you’re using. For example:
sudo port install mysql56 +openssl
or:
sudo port install mariadb +openssl
__
Thank you, much appreciated.
Tony S. Wu
tonyswu@gmail.com
On Feb 28, 2014, at 3:36 PM, Ryan Schmidt wrote:
>
> On Feb 28, 2014, at 17:16, Tony S. Wu wrote:
>
>> Is there a port for MySQL Server that is built with SSL support?
>
> Select the +openssl variant of whatever mysql port yo
Hi,
Is there a port for MySQL Server that is built with SSL support?
Thanks,
Tony S. Wu
tonyswu@gmail.com
smime.p7s
Description: S/MIME cryptographic signature
___
macports-users mailing list
macports-users@lists.macosforge.org
https://lists
Hi,
> - when updating an existing port, is it recommended to copy in your own depot
> (own user) or work on the existing one (as root)? in the first case, it
> seems that not all action are prioritizing repositories in the same order
> (install and before).
I'd recommend copying it so
(1) you ca
At 10:43 AM -0500 2/28/14, Julien T wrote:
- there is a startupitem option but it does not seem any way to
include a cron-like job through launchd? script/exec to launch every
day/month. So I suppose for now, we include our own file.
I won't try to handle all your questions! ;)
launchd handl
Hello,
I have several Portfile in the pipe and more questions arising which don't
find solutions in the guide.
- when updating an existing port, is it recommended to copy in your own
depot (own user) or work on the existing one (as root)? in the first case,
it seems that not all action are priori
[Sorry, I realise I send my replies off-list]
On 28 Feb 2014, at 14:44, Jason Swails wrote:
> On Fri, 2014-02-28 at 14:33 +0100, Peter Danecek wrote:
>> Hi all,
>>
>> I observe a behaviour, which I believe is due to the fact that I
>> uninstalled an selected port (see below). This seems to lea
[Sorry, I realise I send my replies off-list]
On 28 Feb 2014, at 15:17, Jason Swails wrote:
> An alternative when you know that you are uninstalling a port is to
> select none. So something like
>
> sudo port select --set postgresql none
>
> to get rid of the simlinks, then another
>
> sudo
[Sorry, I realise I send my replies off-list]
On 28 Feb 2014, at 15:38, Clemens Lang wrote:
> Hi,
>
>> I believe it is consistent. As I understand it, the simlinks created by
>> "port select" are not *owned* by the selected port. Since the port
>> itself does not maintain these simlinks (but
Hi,
I'm pleased to announce that The MacPorts Project has been accepted into Google
Summer of Code 2014 [1] -- a program where Google pays students to work for
Open Source projects over the summer. If you're a student in higher education
or know somebody who is and would be interested in workin
Hi,
> I believe it is consistent. As I understand it, the simlinks created by
> "port select" are not *owned* by the selected port. Since the port
> itself does not maintain these simlinks (but rather 'port select' does),
> there are good arguments to be made that the port should _not_ own
> sim
On Fri, Feb 28, 2014 at 9:30 AM, Peter Danecek wrote:
>
> On 28 Feb 2014, at 15:17, Jason Swails wrote:
>
> > An alternative when you know that you are uninstalling a port is to
> > select none. So something like
> >
> > sudo port select --set postgresql none
> >
> > to get rid of the simlinks,
On Fri, 2014-02-28 at 14:53 +0100, Peter Danecek wrote:
> On 28 Feb 2014, at 14:44, Jason Swails wrote:
>
> > On Fri, 2014-02-28 at 14:33 +0100, Peter Danecek wrote:
> >> Hi all,
> >>
> >> I observe a behaviour, which I believe is due to the fact that I
> >> uninstalled an selected port (see bel
On Fri, Feb 28, 2014 at 8:44 AM, Jason Swails wrote:
> sudo port -f select --set postgresql postgresql93
>
> In my opinion, such protection is a Good Thing (TM). There's a way to
> work around it if you know the reason behind the file collision, but I
> certainly wouldn't want a program (especial
On Fri, 2014-02-28 at 14:33 +0100, Peter Danecek wrote:
> Hi all,
>
> I observe a behaviour, which I believe is due to the fact that I
> uninstalled an selected port (see below). This seems to leave the
> selection mechanism in an undesired state and should be handled. Now I
> wonder which is the
Hi all,
I observe a behaviour, which I believe is due to the fact that I uninstalled an
selected port (see below). This seems to leave the selection mechanism in an
undesired state and should be handled. Now I wonder which is the expected
behaviour, so that I can eventually file a ticket again
I installed the default version of python27 and now it works fine.
Thank you for your help David.
Le 27 févr. 2014 à 16:38, David Evans a écrit :
> On 2/27/14 1:02 AM, Giuseppe Di Matteo wrote:
>> Here it is:
>> echo "import libxml2" | /opt/local/bin/python2.7 -
>>
>> Traceback (most recent ca
18 matches
Mail list logo
