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

Website and Guide automated regen
by Juan Manuel Palacios 14 Dec '07

14 Dec '07

After some work on our subversion server, the trunk/www and trunk/ doc-new dirs have been setup under the watch of a new post-commit hook that does the appropriate dance(s) when commits to either of those (and only those) happen, as opposed to dancing whenever a commit to anywhere in our repo takes place (as it used to be until now, which is obviously a huge waste of resources). I wont be around much for the next couple of days so I wont have a chance to keep my eye on this new system, so I'd love it if those who are committing to those directories kept their eyes open for this new functionality: please report whether or not the guide and/or website reflects your changes a little after you commit them; if not then that's a bug in our infrastructure that we should look into. Thanks for your help! Regards,... -jmpp

1 0

Re: Objection to wikifying the guide
by markd＠macports.org 14 Dec '07

14 Dec '07

I'm afraid my last email had a bad tone and I'm sorry about that. I am rushing to get out of town and I'm afraid I've come off as a bit touchy and angry at Juan. I'm not. So please excuse the tone, Juan and others, and accept my apologies for arguing in such an obtuse fashion. The guide was sortof of my baby but I want others to contribute as they have. I have strong ideas about how it should be done but I should have just kept on making suggestions and tossing things back and forth as normal rather than trying to explain some deep rationale in a hurry, which probably interests few anyway. So Juan I'm sorry I sounded defensive, and doc team (and others) I'm not normally schizophrenic so please don't stop contributing! Everyone have a great Christmas and happy new year and I'll "see" you next year! Mark

1 0

List of universal archs in base (was: [31959] trunk/dports/devel/openssl)
by Ryan Schmidt 14 Dec '07

14 Dec '07

On Dec 12, 2007, at 12:52, mww(a)macports.org wrote: > + post-patch { > +# foreach arch {i386 x86_64 ppc ppc64} > + foreach arch {i386 ppc} { > + file copy ${worksrcpath} ${workpath}/${arch} > + } > + } Perhaps we should define this list of universal architectures in MacPorts base itself, so that ports that want to do something for each arch will already have the array ready to go rather than have to define it themselves -- possibly differently from base, which would be inconsistent. Such a definition (let's call it "universal_archs", maybe) should probably go above the definition of configure.universal_args in portconfigure.tcl. The contents of this array should be used to build up a new variable (how about "universal_arch_flags") which ends up looking like "-arch i386 -arch ppc". This string can then be used to build up configure.universal_cflags, configure.universal_cxxflags and configure.universal_ldflags. Anyone agree? Disagree?

1 0

Re: [32026] trunk/doc-new/guide/xml/installing.xml
by Juan Manuel Palacios 14 Dec '07

14 Dec '07

On Dec 14, 2007, at 1:33 AM, boeyms(a)macports.org wrote: > Revision > 32026 > Author > boeyms(a)macports.org > Date > 2007-12-13 21:33:13 -0800 (Thu, 13 Dec 2007) > Log Message > > doc-newguide/xml/installing.xml: remove note made redundant by > changeset:31985. Maybe that note in particular is now unnecessary, yes, but then I'd suggest linking directly to the selfupdate section of the guide somewhere in the new postflight explanation, so as to provide the necessary follow up. Maybe something like: Once all that is done, the script runs the '<a href="selfupdate- section">selfupdate</a>' action of the 'port(1)' command (...) How does that sound? Regards,... -jmpp

1 0

Re: Ion3 license and possible removal
by Ryan Schmidt 13 Dec '07

13 Dec '07

On Dec 13, 2007, at 16:13, paul beard wrote: > On 12/13/07, Rainer Müller wrote: > >> For me this sounds like a removal request... What is the problem >> with a >> version more than 28 days old? In my personal opinion ion3 with this >> license addition does not qualify as free software any more. >> Definitely >> remove it. >>> >> > > Wow, from that thread, I would have to agree. for those not > inclined to read through the flamethread, FreeBSD is in a ports > freeze, where updates and changes are verboten, unless they are to > fix an issue like a segfault or the like: these often last a month, > and that would span the 28 days. > > Never heard of ion3 before today, and I guess I won't miss it. Yeah, that's a pretty fantastic thread on the FreeBSD list there. The software has been removed from FreeBSD and will not be added back in: http://lists.freebsd.org/pipermail/freebsd-ports/2007-December/ 045576.html MacPorts should probably remove it too, though I'd suggest leaving the portfile with a message in it that the software is not available through MacPorts and must be installed by hand, explaining why. Just to prevent someone from inadvertently adding it back in later. The message could perhaps also indicate other alternatives that are still available through MacPorts, if we thought that was appropriate. The port revision should be incremented, and users should see the message upon upgrading. I would want to ensure that any existing users of the port are made aware that it is gone; otherwise they would retain the old version forever, which the software author surely does not want.

1 0

Re: [31958] trunk/dports/security/afflib
by Ryan Schmidt 13 Dec '07

13 Dec '07

On Dec 12, 2007, at 12:30, ricci(a)macports.org wrote: > Revision: 31958 > http://trac.macosforge.org/projects/macports/changeset/31958 > Author: ricci(a)macports.org > Date: 2007-12-12 10:30:58 -0800 (Wed, 12 Dec 2007) > > Log Message: > ----------- > fix library install with auto* improvements, now creates a dylib as > well (thanks to pogma@) > improve the configure.ac to shorten the configure script (thanks > again to pogma@) > use autoreconf after the above patches Looks like some big changes. Is there a ticket for this? Have these changes been sent upstream as well?

2 1

1.6.0-rc3 posted for testing (Was: [31952] tags/release_1_6_0-rc3/)
by Juan Manuel Palacios 12 Dec '07

12 Dec '07

No need to say more than quote my commit log below ;-) Thanks to all! -jmpp On Dec 12, 2007, at 1:33 PM, jmpp(a)macports.org wrote: > Revision > 31952 > Author > jmpp(a)macports.org > Date > 2007-12-12 09:33:20 -0800 (Wed, 12 Dec 2007) > Log Message > > Even though most of the changes that have gone into the release > branch since 1.6.0-rc2 was posted are related to scripts > such as postflight, it's still advisable to post another rc for > testing, but hopefully a short lived one this time round. > > In my opinion, the main focus should be the postflight script > itself, it has seen many, many bugfixing changes since I rewrote it, > mostly tcsh related ones. I've tested it very thoroughly locally on > both already customized environments and completely clean ones, > thankfully successfully, so I feel it's ready. But still, I'd > appreciate as many eyes on it as possible, thanks! > Added Paths > > tags/release_1_6_0-rc3/ > Diff > > Copied: tags/release_1_6_0-rc3 (from rev 31951, branches/release_1_6) > > _______________________________________________ > macports-changes mailing list > macports-changes(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-changes

1 0

Easytag2, bug #11456
by Andrew Cho 12 Dec '07

12 Dec '07

Hi, What do I need to do to get the portfile from this ticket commited? I realize some of the syntax for ports has changed since I modified the original easytag 1.1 port to build easytag 2.1. Is there anything special I need to keep in mind? -Andrew

3 6

Meet our brand new documentation! (Fwd: [31887] trunk/www/includes/common.inc)
by Juan Manuel Palacios 12 Dec '07

12 Dec '07

Meet our brand new documentation: http://guide.macports.org Per my commit log below, thanks to all those who made this happen, no need to emphasize what a long way quality documentation can take an open source project. Much appreciated! Daniel, I guess you can now stop hosting it at geeklair. The project is indebted to you for all the bits and bytes in both in bandwidth and processing power you've donated! ;-) Regards,... -jmpp Begin forwarded message: > From: jmpp(a)macports.org > Date: December 11, 2007 2:40:41 AM GMT-04:00 > To: macports-changes(a)lists.macosforge.org > Subject: [31887] trunk/www/includes/common.inc > Reply-To: macports-dev(a)lists.macosforge.org, jmpp(a)macports.org > > Revision 31887 > Author jmpp(a)macports.org > Date 2007-12-10 22:40:39 -0800 (Mon, 10 Dec 2007) > Log Message Our project guide is now live at the canonical > guide.macports.org URL. Thanks mainly to Mark, Simon and Maun Suang > for the hard work invested in writing our high quality > documentation! Thanks to Daniel for hosting it for us temporarily- > very-long! And finally thanks to Bill for publishing it officially > for us, much appreciated!

5 5

Re: [31766] trunk/dports/audio/libao
by Ryan Schmidt 12 Dec '07

12 Dec '07

On Dec 6, 2007, at 13:27, saispo(a)macports.org wrote: > Modified: trunk/dports/audio/libao/Portfile > =================================================================== > --- trunk/dports/audio/libao/Portfile 2007-12-06 18:47:51 UTC (rev > 31765) > +++ trunk/dports/audio/libao/Portfile 2007-12-06 19:27:22 UTC (rev > 31766) > @@ -2,8 +2,8 @@ > > PortSystem 1.0 > name libao > -version 0.8.6 > -revision 2 > +version 0.8.8 > +revision 1 Don't change this now, but remember for next time that the first revision of a given port version is 0, not 1. In the future, just remove the revision line when upgrading a port's version to get the default revision of 0. > -patchfiles patch-AU-configure patch-AU- > src__plugins__macosx__ao_macosx.c > +patchfiles patch-configure Patchfiles should be named "patch-whatever.diff". See "port lint". Also, you removed references to some patchfiles, but didn't remove the patchfiles themselves....?

4 5