Re: malloc

On Mar 19, 2007, at 10:29 PM, Yves de Champlain wrote: Hi There is no malloc.h in Darwin, but everything malloc.h provides is provided (I'm sure) by libSystem (I think) malloc.h is a "Linuxism" that personally I do not understand, there's stdlib.h containing all the needed memory allocat

Re: "Trac does not send email unless you list the address in the CC field": update wiki?

On Mar 19, 2007, at 4:38 AM, Ryan Schmidt wrote: That explains the delay in the review of the tickets that I've submitted; thanks to Elias Pipping for trawling through them :-) Could the wiki be updated appropriately? Did it! Thanks for reminding me. Hello Ryan! Could I please ask you

Re: Beginner questions

On Mar 17, 2007, at 7:59 PM, Stefan Bruda wrote: o Does MacPorts logs anything? nope (at least not currently). It is a pitty in my opinion, This feature is planned for a future release, its design still a bit up in the air and in the heads of some of us as still-in-need-of-implementa

Re: GrADS

On Mar 16, 2007, at 11:17 AM, Takeshi Enomoto wrote: post-destroot { xinstall -d -m 755 ${destroot}${prefix}/share/${name}/ foreach file [glob -directory ${workpath} *.dat *res] { file rename ${file} ${destroot}${prefix}/share/${name}/ file link -symbolic ${destroot}${p

Re: Pallet

CFLib is not used by the rest of the base system. At the time, Landon and I were planning to use it to perform bundle and plist manipulation to create .pkg bundles, and other Mac OS X-specific actions. - Kevin On Mar 19, 2007, at 11:27 PM, Juan Manuel Palacios wrote: On Mar 14, 2007, a

Re: Pallet

On Mar 14, 2007, at 9:40 PM, Randall Wood wrote: How does CFLib in the base/src directory get used? Not entirely sure what its original intent was (other than a bridging between CoreFoundation and TLC), but I do know that currently MacPorts does not employ the CFLib code in any way... or

malloc

Hi There is no malloc.h in Darwin, but everything malloc.h provides is provided (I'm sure) by libSystem (I think) However, configure will always fail looking for malloc.h, so wouldn't it be a good idea to have macports install a dummy malloc.h ? Or, in other words maybe, why is there no

Re: emacs-devel and build flags (was: [22884] trunk/dports/editors/emacs-devel/Portfile)

On Mar 19, 2007, at 1:15 PM, Elias Pipping wrote: Shouldn't -I${prefix}/include be only in CPPFLAGS? Although that *should* be true that's not always sufficient. IMHO, it is better to avoid setting CFLAGS, as this may disable optimizations nad/or debug information (not checked). i believe

Re: emacs-devel and build flags (was: [22884] trunk/dports/editors/emacs-devel/Portfile)

On Mar 19, 2007, at 4:39 PM, Vincent Lefevre wrote: On 2007-03-17 13:00:50 -0700, [EMAIL PROTECTED] wrote: Revision: 22884 http://trac.macosforge.org/projects/macports/changeset/ 22884 Author: [EMAIL PROTECTED] Date: 2007-03-17 13:00:49 -0700 (Sat, 17 Mar 2007) Log Message: -

Re: [22929] trunk

On Mar 19, 2007, at 12:25 PM, Randall Wood wrote: 1) Do not commit changes against trunk. you're confused (and so am I). I use svk, it has improved merge support and adds the svk:merge property on trunk/ when I merge things in. A) The email subject lines are totally non-descriptive, re

Re: [22929] trunk

Two things: 1) Do not commit changes against trunk. A) The email subject lines are totally non-descriptive, reading "[change#] trunk" instead of "[change#] trunk/dports/gnome/libgnomekbd" as it would if the commit was done in that port's directory instead of in trunk. B) Committing a c

emacs-devel and build flags (was: [22884] trunk/dports/editors/emacs-devel/Portfile)

On 2007-03-17 13:00:50 -0700, [EMAIL PROTECTED] wrote: > Revision: 22884 > http://trac.macosforge.org/projects/macports/changeset/22884 > Author: [EMAIL PROTECTED] > Date: 2007-03-17 13:00:49 -0700 (Sat, 17 Mar 2007) > > Log Message: > --- > * cleanup > > Modified Paths:

Re: php5 +memcache

oops, ryan ... i goofed. turns out the macports memcached port is only the daemon and doesnt include the php extension. sorry, i should have made sure it was working for me first. no big deal if you already added the variant though -- php works fine without the extension installed (just c

Re: fftw3

Ryan, Thanks for letting me know of fftw-3. I can maintain this. Mine has a g95 variant. I'd happy if you consider adding this. I submitted a portfile for fftw-3.1.2. fftw-2 and fftw-3 are incompatible so port fftw should remain as it is.

Re: Mutt-devel

On 18/03/07 19:13, Ryan Schmidt wrote: > Had you already sent an email to the maintainer? If you only > submitted the ticket, the maintainer may not have seen it yet; Trac > does not send email unless you list the address in the CC field, > which I have now done. Yes, I forgot to mention I a

Re: [22914] trunk/base/src/port1.0/resources/group

On 19.03.2007, at 09:01, Juan Manuel Palacios wrote: Hey Markus! Are these bug fixes or enhancements to the Python group code? Should they be merged into the 1.4 branch? enhancements; and when I think about it: It really is a very clear (and tiny) improvement, so merging it into 1.4 sh

Re: "Trac does not send email unless you list the address in the CC field": update wiki?

On Mar 19, 2007, at 03:14, Boey Maun Suang wrote: On 19/03/2007, at 11:13, Ryan Schmidt wrote: If you only submitted the ticket, the maintainer may not have seen it yet; Trac does not send email unless you list the address in the CC field Oh, I thought to the contrary, given this part of

"Trac does not send email unless you list the address in the CC field": update wiki?

Hi everyone, On 19/03/2007, at 11:13, Ryan Schmidt wrote: If you only submitted the ticket, the maintainer may not have seen it yet; Trac does not send email unless you list the address in the CC field Oh, I thought to the contrary, given this part of the page at http:// trac.macosforge.o

Re: [22914] trunk/base/src/port1.0/resources/group

Hey Markus! Are these bug fixes or enhancements to the Python group code? Should they be merged into the 1.4 branch? -jmpp On Mar 19, 2007, at 3:32 AM, [EMAIL PROTECTED] wrote: Revision 22914 Author [EMAIL PROTECTED] Date 2007-03-19 00:32:26 -0700 (Mon, 19 Mar 2007) Log Message add spec