December 2007 - macports-dev - lists.macosforge.org

New Ticket button missing
by Ryan Schmidt 03 Dec '07

03 Dec '07

I can't find the New Ticket button in Trac anymore. Where did it go?

3 3

Re: [31659] trunk/dports/games/freeciv
by Ryan Schmidt 03 Dec '07

03 Dec '07

On Dec 1, 2007, at 20:43, rhwood(a)macports.org wrote: > Revision: 31659 > http://trac.macosforge.org/projects/macports/changeset/31659 > Author: rhwood(a)macports.org > Date: 2007-12-01 18:42:54 -0800 (Sat, 01 Dec 2007) > > Log Message: > ----------- > Add patch from Bryan Blackburn to build if bind9 is present. Is there any more information available about this? a ticket? a discussion somewhere? php5 won't build either if bind9 is present, and it would be nice to know if this fix for freeciv will help php5 as well. Thanks.

3 5

Re: propchange - r31680 svn:log
by Juan Manuel Palacios 03 Dec '07

03 Dec '07

On Dec 2, 2007, at 9:24 PM, ryandesign(a)macports.org wrote: > Author: ryandesign(a)macports.org The author here needs to be that of the original revision you're editing, I'll work with Bill this coming week to fix that. -jmpp > > Revision: 31680 > Property Name: svn:log > > New Property Value: > Hard wrap and detab HACKING file. Whitespace changes only.

1 0

Re: [31640] trunk/base
by Ryan Schmidt 03 Dec '07

03 Dec '07

On Nov 30, 2007, at 21:32, jmpp(a)macports.org wrote: > The ChangeLog was orignally meant to be a user-parsable file > listing only major changes to base, so that we could > use it in our release process to advertise our new goodies. > Unfortunately, lately it has turned into a litle bit > of a file tracking commits to base, with a little bit of user level > information and a lot of gaps in between to > do either one right, bleh! > > Therefore add a real user-parsable NEWS file in which new features > and bug fixes for each release will be advertised, > starting with the contents of 1.6.0 > > Here's hoping that from now on the ChangeLog will turn into a file > that truly tracks commits to base, with proper revision > numbers for each entry and ticket numbers in case of bug fixes, > after being spared from having to remain user-parsable. Can't people who are interested in that kind of information just read the Subversion log? I don't want to have to bother with updating the ChangeLog every time I change something on base. Granted, it's not that often for me. But for others who make many changes on base, this would seem to be annoying.

2 1

Meet our new website
by Juan Manuel Palacios 02 Dec '07

02 Dec '07

Say hello: http://www.macports.org/ Thanks a bunch to Bill for making this happen, much appreciated! As always, feedback is welcome. I'll announce our new web presence to a broader audience together with the release of 1.6.0, which I'm putting together as we spea.... sorry, as I write this message ;-) Regards,... -jmpp

3 4

Re: [31663] trunk/dports/python/py25-scientific
by Ryan Schmidt 02 Dec '07

02 Dec '07

On Dec 2, 2007, at 09:29, saispo(a)macports.org wrote: > Revision: 31663 > http://trac.macosforge.org/projects/macports/changeset/31663 > Author: saispo(a)macports.org > Date: 2007-12-02 07:28:44 -0800 (Sun, 02 Dec 2007) > > Log Message: > ----------- > Fix py25-scientific on Leopard using py25-numeric patch, ticket > #13113 can be closed > > Modified Paths: > -------------- > trunk/dports/python/py25-scientific/Portfile In this commit, you've fixed py25-scientific, but ticket #13113 is about py25-ipython...

1 0

Fwd: Added support in MacPorts base to set PATH and MANPATH automatically in Leopard
by Randall Wood 02 Dec '07

02 Dec '07

Oops. Hit reply instead of reply all... ---------- Forwarded message ---------- From: Randall Wood <randall.h.wood(a)alexandriasoftware.com> Date: Dec 2, 2007 3:41 PM Subject: Re: Added support in MacPorts base to set PATH and MANPATH automatically in Leopard To: Juan Manuel Palacios <jmpp(a)macports.org> On 12/2/07, Juan Manuel Palacios <jmpp(a)macports.org> wrote: > > > On Dec 2, 2007, at 2:06 PM, James Berry wrote: > > > Hi Juan, > > > > On Dec 2, 2007, at 9:50 AM, Juan Manuel Palacios wrote: > >> So, has any conclusion been reached for this issue? I'm inclined > >> to backing this feature out of the release_1_6 branch until a > >> working consensus is reached, and only release it to the public at > >> that time (in 1.6.x (x > 0)). Until now we've only been modifying > >> the user "profile" for a range of bourne based shells and the > >> "cshrc" file for equivalent C based shells, which has worked fairly > >> well, I believe; anyone experienced enough to create something like > >> ~/.bash_profile or anything else very shell specific would be savvy > >> enough to setup his/her own environment to their content, I'm sure. > >> I'd strongly favor sticking to this approach in 1.6.0 until > >> something better is found, unless it explicitly breaks expected > >> behavior on Leopard. Does it? > > > > Well, given that man pages are broken at present with a standard > > MacPorts install under Leopard, something has to be done. A few > > choices: > > > > (1) Use this scheme, as implemented. (Downsides: affects /etc, > > MacPorts paths are added at the end of PATH and MANPATH). > > > I'm uncomfortable with this approach, as already noted in my > previous > mail. If Apple provides a mechanism for third-party developers to append paths to PATH and MANPATH without changing any user or system-installed file, then I think we should use it. We may want though (if this would work--I don't know if symlinks would be honored or if only real files would be honored by this mechanism) to use symlinks from /opt/local/etc/[man]path.d/macports to /etc/[man]path.d/macports instead of placing files in /etc/[man]path.d and provide a simple tool (like macports-path-util) to allow users to add/remove those symlinks > > > > > (2) Supplement this scheme by munging PATH inside the MacPorts > code > > to ensure that $prefix is always at the head of the path during > > builds, and to guard against the sort of build problems suggested by > > kvv. > > > MacPorts already sets its internal path for a few things, so this > suggestion may be easy to implement but might, just might, have > repercussions that we may want to test more thoroughly (not on the > verge of a release, in my opinion ;-) > > > > > > > (3) Modify existing path modification code to also add MacPorts > > paths to MANPATH. (This might break other man pages on Tiger where > > the system provides no meaningful default for MANPATH—maybe we do it > > only if MANPATH is already defined?) > > > I could definitely look into this extension to the existing > postflight script and its implications on both Leopard and Tiger, I > like its "lowest risk" approach. In this case I'll remove the /etc/ > paths.d and /etc/manpaths.d munging code from the release_1_6 branch > to safeguard the release, but will not touch it in trunk so that we > can continue brainstorming over it there. > > Any other suggestions? > > Regards,... > > > -jmpp > > _______________________________________________ > macports-dev mailing list > macports-dev(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-dev > -- Randall Wood randall.h.wood(a)alexandriasoftware.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy." -- Randall Wood randall.h.wood(a)alexandriasoftware.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."

1 0

ChangeLog and NEWS file (Re: [31640] trunk/base)
by Juan Manuel Palacios 02 Dec '07

02 Dec '07

So, I'm now putting the 1.6.0 release together finally, but I have a few comments I'd like to make to this list. First and foremost, take a look at my r31640 commit, quoted below: On Nov 30, 2007, at 11:32 PM, jmpp(a)macports.org wrote: > Revision > 31640 > Author > jmpp(a)macports.org > Date > 2007-11-30 19:32:13 -0800 (Fri, 30 Nov 2007) > Log Message > > The ChangeLog was orignally meant to be a user-parsable file listing > only major changes to base, so that we could > use it in our release process to advertise our new goodies. > Unfortunately, lately it has turned into a litle bit > of a file tracking commits to base, with a little bit of user level > information and a lot of gaps in between to > do either one right, bleh! > > Therefore add a real user-parsable NEWS file in which new features > and bug fixes for each release will be advertised, > starting with the contents of 1.6.0 > > Here's hoping that from now on the ChangeLog will turn into a file > that truly tracks commits to base, with proper revision > numbers for each entry and ticket numbers in case of bug fixes, > after being spared from having to remain user-parsable. ---snip (you can find the newly added NEWS file in base/NEWS)--- From now on I would like to request that, as noted in this commit log, any change made to base is recorded in the ChangeLog, with precise revision(s) information and Trac ticket number(s) if you're fixing a bug(s). The best way to accomplish this is to simply incorporate this bit in your commit right away, so that you don't have to come back to the ChangeLog who-knows how long after when you might have forgotten the details. I (or anyone else coordinating releases) will handle the NEWS file at release time, after discussing what part of the changes should be advertised for user consumption, so don't worry about that. So, in short, don't be shy to add to the ChangeLog an entry for your every single commit to base, but please be thorough when you do. Thanks! Secondly, about the NEWS file, there's this commit about which I didn't exactly know what to say: http://trac.macports.org/projects/macports/changeset/30216 Markus, are those Portfile level options that Portfile writers will be able to use? No...? What then? Thirdly, one other thing I didn't add to the NEWS file is our support for /etc/paths.d/ and /etc/manpaths.d/ config options, as I haven't been able to keep up with that thread. I'll amend as soon as I get a chance. Some other things might come up, but my mind is on five things right now and I'm forgetting. Please do alert me to anything about 1.6.0 I might be missing, thanks! Regards,... -jmpp

2 3

Re: [31625] trunk/dports/lang/scala/Portfile
by Ryan Schmidt 02 Dec '07

02 Dec '07

On Nov 30, 2007, at 15:14, blair(a)macports.org wrote: > Revision: 31625 > http://trac.macosforge.org/projects/macports/changeset/31625 > Author: blair(a)macports.org > Date: 2007-11-30 13:14:51 -0800 (Fri, 30 Nov 2007) > > Log Message: > ----------- > New upstream 2.6.1-RC1 release of Scala. > > Modified Paths: > -------------- > trunk/dports/lang/scala/Portfile > > Modified: trunk/dports/lang/scala/Portfile > =================================================================== > --- trunk/dports/lang/scala/Portfile 2007-11-30 19:49:21 UTC (rev > 31624) > +++ trunk/dports/lang/scala/Portfile 2007-11-30 21:14:51 UTC (rev > 31625) > @@ -2,7 +2,7 @@ > > PortSystem 1.0 > name scala > -version 2.6.0 > +version 2.6.0.2.6.1.rc1 Out of curiosity, why not "version 2.6.1-rc1"? Is there a MacPorts base bug you're working around by using this made-up version number?

2 1

Re: [31624] trunk/doc-new/guide/xml/portfile-global-keywords.7.xml
by Ryan Schmidt 02 Dec '07

02 Dec '07

On Nov 30, 2007, at 13:49, simon(a)macports.org wrote: > - <programlisting>homepage http://www.somesite.org/apps</ > programlisting> > + <programlisting>homepage http://www.somesite.org/apps</ > programlisting> The web site "www.somesite.org" is owned by a domain squatter. The correct web site address to use in examples and documentation is "www.example.(com|net|org)". These are reserved for examples. See section 3 of RFC 2606. http://www.ietf.org/rfc/rfc2606.txt

2 1