Re: [MacPorts] #5816: UPDATE: postgresql8

2016-03-24 Thread Lachlan Deck
Is that what I was doing 10 years ago :)

> On 25 Mar 2016, at 2:27 AM, MacPorts  wrote:
> 
> #5816: UPDATE: postgresql8
> -+
>  Reporter:  lachlan.deck@…  |  Owner:  mww@…
>  Type:  enhancement | Status:  closed
>  Priority:  Normal  |  Milestone:
> Component:  ports   |Version:  1.0
> Resolution:  fixed   |   Keywords:
>  Port:  postgresql8 |
> -+
> Changes (by ryandesign@…):
> 
> * priority:  High => Normal
> * type:  defect => enhancement
> * port:   => postgresql8
> 
> 
> Old description:
> 
>> ---
>> /opt/local/var/db/dports/sources/rsync.rsync.opendarwin.org_dpupdate_dports/databases/
>> postgresql8/Portfile  2005-1
>> 1-08 10:45:18.0 +1100
>> +++ Portfile_postgresql82005-11-24 14:14:36.0 +1100
>> @@ -98,6 +98,16 @@
>>configure.env-appendPYTHON=${prefix}/bin/python2.4
>> }
>> 
>> +variant krb5 {
>> +   depends_lib-append  bin:kerberos:kerberos5
>> +   configure.args-append   --with-krb5
>> +}
>> +
>> +variant perl {
>> +   depends_lib-append  bin:perl:perl5.8
>> +   configure.args-append   --with-perl
>> +}
>> +
>> platform darwin 8 {
>>configure.env-appendCC=/usr/bin/gcc-4.0 CPP=/usr/bin/cpp-4.0
>> CXX=/usr/bin/g++-4.0
>> }
>> @@ -125,7 +135,7 @@
>>post-install {
>>ui_msg "\nTo create a database instance, after install
>> do\n\
>>sudo mkdir -p ${dbdir}\n\
>> -   sudo chown ${dbuser}:postgre ${dbdir}\n\
>> +   sudo chown ${dbuser}:{$dbgrp} ${dbdir}\n\
>>sudo su ${dbuser} -c \'${libdir}/bin/initdb -D
>> ${dbdir}\'"
>>ui_msg "\nTo activate the PostgreSQL8 server, add\n\
>>POSTGRESQL8=-YES-\n\
> 
> New description:
> 
> {{{
> ---
> /opt/local/var/db/dports/sources/rsync.rsync.opendarwin.org_dpupdate_dports/databases/postgresql8/Portfile
> 2005-11-08 10:45:18.0 +1100
> +++ Portfile_postgresql82005-11-24 14:14:36.0 +1100
> @@ -98,6 +98,16 @@
> configure.env-appendPYTHON=${prefix}/bin/python2.4
>  }
> 
> +variant krb5 {
> +   depends_lib-append  bin:kerberos:kerberos5
> +   configure.args-append   --with-krb5
> +}
> +
> +variant perl {
> +   depends_lib-append  bin:perl:perl5.8
> +   configure.args-append   --with-perl
> +}
> +
>  platform darwin 8 {
> configure.env-appendCC=/usr/bin/gcc-4.0 CPP=/usr/bin/cpp-4.0
> CXX=/usr/bin/g++-4.0
>  }
> @@ -125,7 +135,7 @@
> post-install {
> ui_msg "\nTo create a database instance, after install
> do\n\
> sudo mkdir -p ${dbdir}\n\
> -   sudo chown ${dbuser}:postgre ${dbdir}\n\
> +   sudo chown ${dbuser}:{$dbgrp} ${dbdir}\n\
> sudo su ${dbuser} -c \'${libdir}/bin/initdb -D
> ${dbdir}\'"
> ui_msg "\nTo activate the PostgreSQL8 server, add\n\
> POSTGRESQL8=-YES-\n\
> }}}
> 
> --
> 
> -- 
> Ticket URL: 
> MacPorts 
> Ports system for OS X

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: MacPorts adding "default" flag to sources.conf

2016-03-24 Thread Rainer Müller
On 2016-03-24 08:09, Ryan Schmidt wrote:
> On Mar 23, 2016, at 1:49 PM, Rainer Müller wrote:
>> That's some broken logic in the upgrade script. It always adds [default]
>> to the first entry that points to the official ports tree if no entry
>> before had this flag. We would need multiple passes over the lines to
>> first check whether [default] exists already.
>>
>> https://trac.macports.org/browser/trunk/base/src/upgrade_sources_conf_default.tcl.in
>>
>> Since it has been 7 years after the introduction of this flag, may I
>> suggest we just remove it instead of rewriting this script?
> 
> You mean, remove the upgrade script? On the assumption that everyone has 
> already upgraded and already has a default set at this point? Sure.

Sorry that was ambiguous. Yes, I mean removing the upgrade script.

Rainer
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Request for help with debugging a CMake-based installation of Geant4

2016-03-24 Thread Mojca Miklavec
Hi,

I'm a bit stuck with geant4.10.2 that is using CMake-based
installation. Version 4.10.1 works fine, but version 4.10.2 installs
wrong links to libraries.

I'm using
-DCMAKE_INSTALL_LIBDIR=${prefix}/lib/Geant4/Geant4.10.2
and the libraries end up at the proper location, but the links are not:

> otool -L /opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib
/opt/local/lib/Geant4/Geant4.10.2/libG4FR.dylib:
/opt/local/lib/libG4FR.dylib
/opt/local/lib/libG4vis_management.dylib
...

I'm a bit stuck. There are of course two solutions, either fixing the
CMake sources or running install_name_tool in post-destroot phase. If
I give up with finding the proper patch, I can always try the hack and
fix links.

Any help would be greatly appreciated.

Ticket:
https://trac.macports.org/ticket/50426

Thank you,
Mojca
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev


Re: MacPorts adding "default" flag to sources.conf

2016-03-24 Thread Ryan Schmidt
On Mar 23, 2016, at 1:49 PM, Rainer Müller wrote:

> On 2016-03-23 15:10, Mojca Miklavec wrote:
>> In sources.conf I have
>> 
>> file:path/to/sparse/svn/checkout/dports [nosync]
>> file:///path/to/another/svn/checkout/dports [nosync]
>> rsync://rsync.macports.org/release/tarballs/ports.tar [default]
>> 
>> But whenever I configure, make and make install the base from trunk, I
>> end up with "default" being added to the first entry, like this:
>> 
>> file:path/to/sparse/svn/checkout/dports [nosync,default]
>> file:///path/to/another/svn/checkout/dports [nosync]
>> rsync://rsync.macports.org/release/tarballs/ports.tar [default]
>> 
>> and then:
>>Warning: More than one default port source is defined.
>> 
>> What's the reason for that weird behaviour?
> 
> That's some broken logic in the upgrade script. It always adds [default]
> to the first entry that points to the official ports tree if no entry
> before had this flag. We would need multiple passes over the lines to
> first check whether [default] exists already.
> 
> https://trac.macports.org/browser/trunk/base/src/upgrade_sources_conf_default.tcl.in
> 
> Since it has been 7 years after the introduction of this flag, may I
> suggest we just remove it instead of rewriting this script?

You mean, remove the upgrade script? On the assumption that everyone has 
already upgraded and already has a default set at this point? Sure.

___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev