Re: New HowTo: Sharing Archives

On Aug 3, 2011, at 00:06, Arno Hautala wrote: > I've just published a new HowTo on the Wiki regarding signing and > sharing archives under MacPorts 2. You're talking about this: https://trac.macports.org/wiki/howto/ShareArchives2 > I'd appreciate a few eyes looking over it for accuracy and cl

Re: New HowTo: Sharing Archives

On Wed, Aug 3, 2011 at 04:07, Ryan Schmidt wrote: > > You're talking about this: > > https://trac.macports.org/wiki/howto/ShareArchives2 I always forget the most important piece right? > Please pick a different suggested location for the keys that is not within > /usr/local. Good point. I'd co

GNU Parallel (#30401)

Hi, Could the patch provided at https://trac.macports.org/ticket/30401 be rolled into the port, please? Or is more work on it required? Russell ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinf

Re: GNU Parallel (#30401)

> Could the patch provided at > > https://trac.macports.org/ticket/30401 > > be rolled into the port, please? Or is more work on it required? r81659. ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/li

Re: base bug?

Hi Marko, On 08/02/2011 10:57 PM, Marko Käning wrote: I just noticed this strange function nameing in darwintrace.c at line 961which shows up with the warning " '$' in identifier or number" --- int stat$INODE64(const char * path, struct stat64 * sb) { return stat64(path, sb); } -

Re: base bug?

On 2011-8-4 01:09 , Rainer Müller wrote: > Hi Marko, > > On 08/02/2011 10:57 PM, Marko Käning wrote: >> I just noticed this strange function nameing in darwintrace.c at line >> 961which shows up with the warning >> >> " '$' in identifier or number" >> >> --- >> int stat$INODE64(const char * pa

Re: New HowTo: Sharing Archives

On Aug 3, 2011, at 1:32 AM, Arno Hautala wrote: > On Wed, Aug 3, 2011 at 04:07, Ryan Schmidt wrote: >> >> You're talking about this: >> >> https://trac.macports.org/wiki/howto/ShareArchives2 > > I always forget the most important piece right? > >> Please pick a different suggested location f

Updated Digikam port, please commit

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I just updated the Digikam port to version 2.0.0 and submitted it in ticket #30576 . It would be nice if someone could commit the changes in the next days. (But not that there are some patches from other tic

Re: New HowTo: Sharing Archives

On Wed, Aug 3, 2011 at 11:37, Bradley Giesbrecht wrote: > > You use "/opt/local" throughout the document except for a few cases where you > use "${prefix}". > For readability consider using "/opt/local" everywhere and add a blurb at the > top "This document assumes the default MacPorts install p

Re: MacPorts is hijacking account on MacOSXServer

Hello Kevin, On 07/28/2011 07:50 PM, kevin beckford wrote: You should familiarize yourself with the operating system you are tasked with writing software on in that case. Or, say "We did not bother to do our homework, don't use our stuff." You said the same thing about git. Ignorance is hardly

MPAB question

t building again Building ktoblzcheck (4 of 5)...package found, not building again Building aqbanking (5 of 5)...package found, not building again Ports built successfully:5 Ports failed:0 All logs are located in /Users/marko/.macports/macports/contrib/mpab/logs-20110803-211243 ---

Re: MPAB question

>From what I recall, the chroot was indefinitely dropped due to it not working in Snow Leopard. ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev

Re: [81673] trunk/dports/cross/lpc21isp/Portfile

Can anyone let me know if CFLAGS=-mmacosx-version-min=10.5 was the right way to go here? smime.p7s Description: S/MIME cryptographic signature ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo