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

registry::installed function
by Randall Wood 13 Oct '07

13 Oct '07

The registry installed function returns a list of lists, the structure of which I don't understand to my satifaction. Given the two resulting entries returned by install, I gather the following: "pidgin 2.0.2 0 +msn 1 0", "pkgconfig 0.22 0 {} 1 0", The string is "$name $version $revision $variants $active $whatIsThis" $variants seems to be either an empty list, a string with a single variant, or a list or variants I do not know what $whatIsThis is. Looking at the source code of $ {prefix}/share/macports/Tcl/registry1.0/receipt_flat.tcl it seems that $whatIsThis is always a zero. What is it? Randall Wood rhwood(a)mac.com http://shyramblings.blogspot.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."

1 0

PortIndex Regen Failure on Saturday 2007-10-13 at 03:30:01
by mp-user＠geeklair.net 13 Oct '07

13 Oct '07

svn: Commit failed (details follow): svn: Can't create directory '/svn/repositories/macports/db/transactions/29860-1.txn': No space left on device SVN commit failed.

1 0

Re: [29852] trunk/dports/x11/xfe/Portfile
by Ryan Schmidt 12 Oct '07

12 Oct '07

On Oct 12, 2007, at 08:27, source_changes(a)macosforge.org wrote: > Revision: 29852 > http://trac.macosforge.org/projects/macports/changeset/29852 > Author: afb(a)macports.org > Date: 2007-10-12 06:27:47 -0700 (Fri, 12 Oct 2007) > > Log Message: > ----------- > append flags instead of replace them... > > Modified Paths: > -------------- > trunk/dports/x11/xfe/Portfile > > Modified: trunk/dports/x11/xfe/Portfile > =================================================================== > --- trunk/dports/x11/xfe/Portfile 2007-10-12 10:43:45 UTC (rev 29851) > +++ trunk/dports/x11/xfe/Portfile 2007-10-12 13:27:47 UTC (rev 29852) > @@ -24,8 +24,8 @@ > depends_lib lib:libFOX-1.6:fox lib:libpng:libpng port:freetype > > configure.args --with-included-gettext --enable-release > -configure.cppflags -I${prefix}/include/freetype2 > -configure.ldflags -L/usr/X11R6/lib > +configure.cppflags-append -I${prefix}/include/freetype2 > +configure.ldflags-append -L/usr/X11R6/lib > configure.env LIBS="-lX11 -lXft" > post-configure { > reinplace "s;/usr/local/share;${prefix}/share;" \ By the way, wouldn't it be a good idea to use ${x11prefix} here instead of hardcoding /usr/X11R6?

1 0

MacPorts website scheduled downtime Friday morning
by James Berry 12 Oct '07

12 Oct '07

The MacPorts web presence may be down for a (hopefully shor)t period of time on Friday morning, about 9:00 am US/Pacific. The macosforge team is moving the web server that serves MacPorts to a new machine and ip address, and it may take DNS a little while to settle across the move. (DNS TTL has been set to a minimal time, so I hope the effects will be short). Please join me in thanking William Siegrist and the rest of the macosforge and apple crew for our great infrastructure. James

3 4

Re: [29842] trunk/dports/mail/pgp5/Portfile
by Randall Wood 12 Oct '07

12 Oct '07

Is there any reason not to simply remove this port from the tree? On 12 Oct 2007, at 02:59, source_changes(a)macosforge.org wrote: > Revision 29842 Author ryandesign(a)macports.org Date 2007-10-11 > 23:59:29 -0700 (Thu, 11 Oct 2007) Log Message pgp: add a note that > users probably don't want this software Modified Paths > trunk/dports/mail/pgp5/Portfile > Diff > Modified: trunk/dports/mail/pgp5/Portfile (29841 => 29842) --- > trunk/dports/mail/pgp5/Portfile 2007-10-11 23:35:49 UTC (rev 29841) > +++ trunk/dports/mail/pgp5/Portfile 2007-10-12 06:59:29 UTC (rev > 29842) @@ -17,6 +17,7 @@ PGP 5.0 contains support for new > encryption methods (most notably \ DSS/Diffie-Hellman), and built- > in keyserver support. Also, the \ command line has been redesigned > to be more Unix and scripting \ - friendly. + friendly. Note: this > software is old; you probably want gnupg or \ + gnupg2 instead. > patchfiles pgpFullLicense.c-patch > _______________________________________________ > macports-changes mailing list > macports-changes(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-changes Randall Wood rhwood(a)mac.com http://shyramblings.blogspot.com "The rules are simple: The ball is round. The game lasts 90 minutes. All the rest is just philosophy."

2 1

Re: [29835] trunk/dports/python/py25-libxml2
by Ryan Schmidt 11 Oct '07

11 Oct '07

On Oct 11, 2007, at 08:36, source_changes(a)macosforge.org wrote: > Revision: 29835 > http://trac.macosforge.org/projects/macports/changeset/29835 > Author: nox(a)macports.org > Date: 2007-10-11 06:36:52 -0700 (Thu, 11 Oct 2007) > > Log Message: > ----------- > py25-libxml2: > * Changed docdir name into a versioned one. > * Changed homepage to something more relevant. > * libxslt is now directly disabled in setup.py, no more hazardous > file delete calls. You've replaced what looks like some simple code in the portfile to delete unwanted files.... with a whole bunch of Python code that will have to be maintained going forward. Is that really better? What was so hazardous about the "file delete" calls? Or is this Python code something that has been submitted upstream? That would be better since then we wouldn't have to maintain it. > Modified Paths: > -------------- > trunk/dports/python/py25-libxml2/Portfile > trunk/dports/python/py25-libxml2/files/patch-setup.py.diff > > Modified: trunk/dports/python/py25-libxml2/Portfile > =================================================================== > --- trunk/dports/python/py25-libxml2/Portfile 2007-10-11 12:11:00 > UTC (rev 29834) > +++ trunk/dports/python/py25-libxml2/Portfile 2007-10-11 13:36:52 > UTC (rev 29835) > @@ -6,16 +6,21 @@ > > name py25-libxml2 > version 2.6.21 > +revision 1 > categories python textproc > platforms darwin > maintainers sfiera openmaintainer > description Python bindings for libxml2 > long_description ${description} > > -homepage http://xmlsoft.org/ > +homepage http://xmlsoft.org/python.html > master_sites ftp://xmlsoft.org/libxml2/python/ > distname libxml2-python-${version} > -checksums md5 229dd2b3d110a77defeeaa73af83f7f3 > + > +checksums md5 229dd2b3d110a77defeeaa73af83f7f3 \ > + sha1 > 2d395e8a5e9accd68f4e78ac2391431ef884e9d5 \ > + rmd160 > d4973576c33e0e65c4fc41b31ee3df5f803abfad > + > patchfiles patch-setup.py.diff > > depends_lib-append port:libxml2 \ > @@ -28,19 +33,13 @@ > } > > post-destroot { > - # strip out anything related to libxslt, so py-libxml2 doesn't > conflict with > - # py-libxslt > - fs-traverse file ${destroot} { > - if {[file isfile ${file}]} { > - if {[string match "*xslt*" ${file}]} { > - file delete ${file} > - } > - } > - } > - xinstall -m 644 -W ${worksrcpath} README TODO \ > - ${destroot}${prefix}/share/doc/${name} > + set docdir ${prefix}/share/doc/${name}-${version} > + xinstall -d ${destroot}${docdir} > + xinstall -m 0644 -W ${worksrcpath} README TODO \ > + ${destroot}${docdir} > } > > livecheck.check md5 > livecheck.url ftp://xmlsoft.org/libxml2/python/ > livecheck.md5 a2cc31311f1b3fb52a08cf1056efda11 > + > > Modified: trunk/dports/python/py25-libxml2/files/patch-setup.py.diff > =================================================================== > --- trunk/dports/python/py25-libxml2/files/patch-setup.py.diff > 2007-10-11 12:11:00 UTC (rev 29834) > +++ trunk/dports/python/py25-libxml2/files/patch-setup.py.diff > 2007-10-11 13:36:52 UTC (rev 29835) > @@ -1,5 +1,5 @@ > ---- setup.py 2005-09-04 19:12:47.000000000 -0400 > -+++ setup.py.new 2007-05-16 07:46:02.000000000 -0400 > +--- setup.py.orig 2007-10-11 15:24:20.000000000 +0200 > ++++ setup.py 2007-10-11 15:24:54.000000000 +0200 > @@ -56,11 +56,7 @@ > # - iconv.h > # - libxslt/xsltconfig.h > @@ -22,3 +22,36 @@ > ] > > xml_files = ["libxml2-api.xml", "libxml2-python-api.xml", > +@@ -122,32 +118,6 @@ > + result.close() > + > + with_xslt=0 > +-if missing("libxslt-py.c") or missing("libxslt.py"): > +- if missing("xsltgenerator.py") or missing("libxslt-api.xml"): > +- print "libxslt stub generator not found, libxslt not built" > +- else: > +- try: > +- import xsltgenerator > +- except: > +- print "failed to generate stubs for libxslt, aborting ..." > +- print sys.exc_type, sys.exc_value > +- else: > +- head = open("libxsl.py", "r") > +- generated = open("libxsltclass.py", "r") > +- result = open("libxslt.py", "w") > +- for line in head.readlines(): > +- if WITHDLLS: > +- result.write(altImport(line)) > +- else: > +- result.write(line) > +- for line in generated.readlines(): > +- result.write(line) > +- head.close() > +- generated.close() > +- result.close() > +- with_xslt=1 > +-else: > +- with_xslt=1 > + > + if with_xslt == 1: > + xslt_includes="" > > _______________________________________________ > macports-changes mailing list > macports-changes(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-changes

3 4

Re: [29735] trunk/dports/x11/gtk-engines2/Portfile
by Yves de Champlain 09 Oct '07

09 Oct '07

Le 07-10-08 à 05:34, source_changes(a)macosforge.org a écrit : > Revision > 29735 > Author > rhwood(a)macports.org > Date > 2007-10-08 02:34:33 -0700 (Mon, 08 Oct 2007) > Log Message > > Update dependencies based on trace output > -depends_build port:p5-xml-parser > > -depends_lib port:gtk2 > +depends_build \ > + port:expat \ > + port:p5-xml-parser \ > + port:perl5.8 > +depends_lib \ > + port:atk \ > + port:cairo \ > + port:fontconfig \ > + port:freetype \ > + port:gettext \ > + port:glib2 \ > + port:gtk2 \ > + port:jpeg \ > + port:libiconv \ > + port:libpng \ > + port:pango \ > + port:tiff Sorry, but does this make any sense at all ? I think all it will do is make the dependency checking phase even longer and the Portfile stuffier. And what about the gnome port ? yves

5 8

New port : GREYCstoration
by Julien Lusson 09 Oct '07

09 Oct '07

Hi ! I've made a port for GREYCstoration (homepage : http:// www.greyc.ensicaen.fr/~dtschump/greycstoration/ ) The ticket for the port : http://trac.macports.org/projects/macports/ticket/12888 It have been tested on my PowerBook G4 with latest MacPorts install (on Tiger) Bye ! Julien

1 0

RubyCocoa, ruby & rb-rubygems
by Eloy Duran 09 Oct '07

09 Oct '07

Hello all, I've had a couple of patches up for a while that add a universal variant to ruby and rb-rubygems. I've added these because I wanted to update the rb-cocoa port. So this is a reminder for these patches: ruby: http://trac.macports.org/projects/macports/ticket/12314 rb-rubygems: http://trac.macports.org/projects/macports/ticket/12317 http://trac.macports.org/projects/macports/ticket/12318 A draft of the rb-cocoa portfile is available at: http://pastie.textmate.org/74998 But actually I would like to take over the maintainership for RubyCocoa. I have send a email to Yuhei about this, but unfortunately haven't heard back. Thing is that the current RubyCocoa port is pretty outdated and since I'm one of the devs of RubyCocoa it might be easier for me to keep it up-to-date. Also if this would be possible I would like to deprecate the name rb-cocoa in favor of rb-rubycocoa. This was already discussed shortly with Ryan Schmidt, is there an update on such functionality? ============================================================ > Now the last patch I have is the one for rubycocoa itself. > But first I would like to now if it's allowed to change the name of > the port? > Because the name of the software is rubycocoa not cocoa.... I think this is still an undefined area. It would be nice if we could just "svn mv rb-cocoa rb-rubycocoa" (if indeed consensus is that this is a good idea) but this would be bad for all users who already have rb-cocoa installed. They would not be informed that their port has been renamed and they would never know if there are any updates unless they later manually install rb-rubycocoa. In some past cases, port authors have kept the portfile under the old name and changed it in some way -- either so that it just outputs an error message advising the user to install the other port, or going so far as to automatically uninstall the old port and installing the new one. The latter seems like a good idea from a user's ease-of-use perspective but the implementation of this feature in those portfiles was deemed scary because MacPorts has no support for this. I think it would be beneficial for MacPorts to have portfile syntax to say that a port has been superseded by a different port. This way all ports like this could be handled identically. We could start with something very simple: a new keyword for portfiles: superseded_by rb-rubycocoa Anyone who tries to install this port gets a message that the port has been replaced by this other one. Anyone who already has the old port installed will see something in "port outdated", and if they try to "port upgrade" the port, they'll get a message advising them to uninstall the current port and install this new port. Then later, if we want, we can look into a process of automatically uninstalling the old port and installing the new one, but we don't need to think about that now. ============================================================ Cheers, Eloy

1 0

List archives not entirely up to date
by Ryan Schmidt 08 Oct '07

08 Oct '07

This page http://lists.macosforge.org/pipermail/macports-users/2007-October/ thread.html shows messages up thru October 8, which is correct. But this page: http://lists.macosforge.org/pipermail/macports-users/2007-October/ only shows messages up thru October 2. What's up with this? Same goes for http://lists.macosforge.org/pipermail/macports-dev/2007-October/ thread.html (which is up to date) and http://lists.macosforge.org/pipermail/macports-dev/2007-October/ (which isn't). Why do we have 2 URLs per mailing list which are supposed to list the same thing, but one of which is out of date? Perhaps one should just be a redirect to the other. Or perhaps there's a pipermail configuration that's amiss.

3 3