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

dp2mp-move branch work done & merging into trunk
by Juan Manuel Palacios 07 Jun '07

07 Jun '07

(same mail as before, resent with a proper subject!) Good afternoon everyone! At long last, I consider the work on my dp2mp-move branch almost 100% done, 99.99% lets say ;-) Here's a doc explaining all the implications moving to these sources has: http://trac.macports.org/projects/macports/wiki/MacPortsRenaming I'd love to get as much feedback as possible on all the renaming and moves, and an overall opinion of how things look like in a standard MacPorts installation after upgrading to this branch. I ask because this branch moves stuff like "/opt/local/var/db/dports/sources/ rsync.rsync.darwinports.org_dpupdate_dports" to "/opt/local/var/ macports/sources/rsync.macports.org/release/ports", as explained in the wiki doc, so if the chosen new paths are not what the majority regards as the best choice, corrections could be easily made before these sources are distributed to the masses. It is my intention to merge all of the branch back into trunk ASAP, after consensus is reached on best "new conventions", since people writing code against current trunk will surely have to rewrite some parts of it after this is merged, albeit changes will hopefully be small. Nevertheless, I'd very much like to minimize this negative (and quite hateful, I understand) side effect. And finally, I say "almost 100%" and not "100%" because there are still a couple of small pending things, detailed in the "Pending" section of the doc. Taking care of them shouldn't take too long at all (remaining 0.01% ;-) Regards,.... -jmpp PS: The branch mirrors trunk minus sfiera's latest commit, which we could easily merge. Therefore merging should be painless, other than the drawback detailed above. Also, branch has been tested extensively and everything works "as expected", but please do not hesitate to send me any feedback/error reports. Thanks!

4 5

NEW: p5-io-multiplex & mailqfmt
by Cyril Bellot 06 Jun '07

06 Jun '07

Hello, could someone commit theses ones : http://trac.macosforge.org/projects/macports/ticket/12061 http://trac.macosforge.org/projects/macports/ticket/12062 Last one may be reviewed first. Thanks

1 0

Subversion repo issue
by Mark Grimes 05 Jun '07

05 Jun '07

Here's one I've never seen before... anyone else having trouble with the MP repo? Now svk does apply props for merge tickets as mentioned prior, and this has always worked before... I suppose I could one-off these commits until I narrow down the problem, but wanted to ask here at the sake of multiple commits per single functional change (email obscurity in this case). ===> Auto-merging (25942, 25943) /local/trunk to /mirror/trunk (base /mirror/trunk:25941). Merging back to mirror source https://svn.macports.org/repository/macports. U dports/net/libdnet/Portfile U dports/perl/p5-xml-apachefop/Portfile U dports/perl/p5-params-util/Portfile U dports/perl/p5-java/Portfile U dports/perl/p5-path-class/Portfile U dports/perl/p5-app-cli/Portfile U dports/perl/p5-pdf-reuse/Portfile U dports/perl/p5-list-moreutils/Portfile U dports/security/ike-scan/Portfile U dports/security/metasploit3/Portfile New merge ticket: e4b2a6a8-e742-4924-8f8a-3771363e925e:/local/trunk:25943 Failed to execute WebDAV PROPPATCH: At least one property change failed; repository is unchanged Mark Grimes, Principal Developer Stateful Labs

3 3

Re: [25845] trunk/dports/devel/dialog/Portfile
by Ryan Schmidt 05 Jun '07

05 Jun '07

On Jun 3, 2007, at 11:09, source_changes(a)macosforge.org wrote: > Revision: 25845 > http://trac.macosforge.org/projects/macports/changeset/25845 > Author: jwa(a)macports.org > Date: 2007-06-03 09:09:05 -0700 (Sun, 03 Jun 2007) > > Log Message: > ----------- > a crude way to solve the problem of having the distfile with always > the > same name - no version number, seems to work even at upgrade > > Modified Paths: > -------------- > trunk/dports/devel/dialog/Portfile > > Modified: trunk/dports/devel/dialog/Portfile > =================================================================== > --- trunk/dports/devel/dialog/Portfile 2007-06-03 15:51:40 UTC (rev > 25844) > +++ trunk/dports/devel/dialog/Portfile 2007-06-03 16:09:05 UTC (rev > 25845) > @@ -21,6 +21,11 @@ > master_sites ftp://invisible-island.net/dialog/ > distname ${name} > worksrcdir ${name}-${version} > + > +pre-fetch { > + file delete -force ${distpath}/${distname}.tar.gz > +} > + > checksums sha1 1912ce21d9590b9fbf85e9159a2f428eaece1894 > configure.args --mandir=${prefix}/share/man Hmm..... won't that cause the archive to be re-downloaded every time you try to install, even if the archive hasn't changed? Isn't there a syntax you can use where you tell MacPorts to store the distfile under a different name?

2 1

dependency bug?
by Vincent Lefevre 05 Jun '07

05 Jun '07

prunille:~> sudo port -v -d uninstall docbook-xml-412 DEBUG: scrollkeeper depends on this port DEBUG: scrollkeeper depends on this port ---> Unable to uninstall docbook-xml-412 4.1.2_0, the following ports depend on it: ---> scrollkeeper ---> scrollkeeper DEBUG: Please uninstall the ports that depend on docbook-xml-412 first. while executing "portuninstall::uninstall $portname [composite_version $portversion [array get variations]] [array get options]" Error: port uninstall failed: Please uninstall the ports that depend on docbook-xml-412 first. but... prunille:~> port info scrollkeeper Warning: Found 2 port scrollkeeper definitions, displaying first one. scrollkeeper 0.3.14, Revision 4, textproc/scrollkeeper (Variants: universal) http://scrollkeeper.sourceforge.net/ ScrollKeeper is a cataloging system for documentation on open systems. It manages documentation metadata (as specified by the Open Source Metadata Framework (OMF) and provides a simple API to allow help browsers to find, sort, and search the document catalog. It will also be able to communicate with catalog servers on the Net to search for documents which are not on the local system. Build Dependencies: pkgconfig, intltool Library Dependencies: libxslt, libxml2, gettext, expat, fontconfig, docbook-xml-scrollkeeper, docbook-xsl, docbook-xml, docbook-xml-4.1.2 Platforms: darwin Maintainers: rhwood(a)macports.org openmaintainer(a)macports.org I don't see docbook-xml-412 in the dependencies. -- Vincent Lefèvre <vincent(a)vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

3 3

GSoC2007 work
by Juan Manuel Palacios 05 Jun '07

05 Jun '07

Afternoon all, again! Sfiera already started work on his GSoC2007 project, so big woot for that! However, he committed to trunk since no decision was ever made on how GSoC work was to be coordinated. I can't stress enough how much I would prefer to see this go into a branch for itself, rather than trunk, since we'll probably have three students committing potentially unstable code to the same place at the same time. We're working with an scm system and rolling back to a working revision is always possible should anything bad happen, I know, but with so many things added it can also be a real pain (considering that some others might also commit new code/bug fixes while GSoC takes place)! Again, many reasons to move GSoC work to branches and very little to have it happen right on trunk, in my opinion. I'll make the move if no one presents a case against it, so please speak up if you feel you have valid arguments against moving to branches. Thanks! Regards,... -jmpp

7 12

Re: [25876] trunk/base/src/registry1.0/receipt_flat.tcl
by Kevin Ballard 05 Jun '07

05 Jun '07

Please don't do this. Our source files really should be using soft tabs if possible, so if we are going to do file-wide changes we should move to that standard. On Jun 4, 2007, at 1:37 AM, source_changes(a)macosforge.org wrote: > Revision > 25876 > Author > boeyms(a)macports.org > Date > 2007-06-04 01:37:35 -0700 (Mon, 04 Jun 2007) > Log Message > > base/sre/registry1.0/receipt_flat.tcl: > * Whitespace changes only (most of the file uses tab characters, > so I'm making > it tab characters only). -- Kevin Ballard http://kevin.sb.org eridius(a)macports.org http://www.tildesoft.com

1 0

Script to obscure your email address in your ports
by Ryan Schmidt 05 Jun '07

05 Jun '07

Dear portfile maintainers, There was a recent discussion on the list in which it was decided that we should support obscuring the email addresses in the maintainer line of our portfiles. If your email address is "bob(a)foo.example.com", then the obscured address entered into the portfile would be "foo.example.com:bob". If your email address ends with @macports.org, then your obscured address is simply the username before the @ sign. A future version of MacPorts will automatically un- obscure the email addresses again for commands like "port info". Some maintainers have already started obscuring their email addresses in their ports. If you would like to obscure your email address in the ports you maintain, you can use the attached script to do so. Assuming you have a Subversion working copy of the ports tree, change to that directory and run the script in that directory with your current maintainer email address as the only argument. The script will obscure the address and swap it out in all your portfiles. You can then examine the output of "svn diff" to ensure the change is correct (and that you have no other unrelated changes in your working copy) and then you can "svn commit" it. # Change to ports tree $ cd /path/to/dports # Make sure there are no other uncommitted changes $ svn status # Make sure we're up to date $ svn update # Obscure maintainer email addresses $ ~/Desktop/portfile-email-fix.sh bob(a)foo.example.com # Check the changes $ svn diff # Commit it $ svn commit -m "Obscuring my email address in the ports I maintain." Caveat: The script will not find any ports of yours where your email address is not on the line that begins with the command "maintainers", for example if the maintainers are split across multiple lines. However, I think there are only four ports to which this applies, and in all four of them, only "openmaintainer(a)macports.org" is on the second line.

1 0

Re: [25816] trunk/dports/graphics/gqview/Portfile
by Ryan Schmidt 04 Jun '07

04 Jun '07

On Jun 2, 2007, at 18:26, source_changes(a)macosforge.org wrote: > Revision: 25816 > http://trac.macosforge.org/projects/macports/changeset/25816 > Author: markd(a)macports.org > Date: 2007-06-02 16:26:50 -0700 (Sat, 02 Jun 2007) > > Log Message: > ----------- > Closes #11833. Remove superfluous configure.env. > > Modified Paths: > -------------- > trunk/dports/graphics/gqview/Portfile > > Modified: trunk/dports/graphics/gqview/Portfile > =================================================================== > --- trunk/dports/graphics/gqview/Portfile 2007-06-02 22:56:09 UTC > (rev 25815) > +++ trunk/dports/graphics/gqview/Portfile 2007-06-02 23:26:50 UTC > (rev 25816) > @@ -3,6 +3,7 @@ > PortSystem 1.0 > name gqview > version 2.0.4 > +revision 1 > categories graphics x11 > platforms darwin > maintainers mvitocruz(a)gmail.com > @@ -14,5 +15,3 @@ > checksums md5 7196deab04db94cec2167637cddc02f9 > depends_lib port:gtk2 > configure.args --mandir=${prefix}/share/man > -configure.env LDFLAGS=-L${prefix}/lib CPPFLAGS=-I${prefix}/ > include \ > - CFLAGS=-flat_namespace There's no mention in the log message or in the ticket notes about why -flat_namespace was removed from the CFLAGS?

1 0

Re: [25869] users/jberry/mpwa
by Ryan Schmidt 04 Jun '07

04 Jun '07

On Jun 4, 2007, at 00:44, source_changes(a)macosforge.org wrote: > Revision: 25869 > http://trac.macosforge.org/projects/macports/changeset/25869 > Author: jberry(a)macports.org > Date: 2007-06-03 22:44:55 -0700 (Sun, 03 Jun 2007) > > Log Message: > ----------- > mpwa: in progress work to support user validation and registration I haven't looked at the code in this revision (or any of the mpwa code, really), but this is going to be a part of the MacPorts web site, yes? I think we should therefore be thinking about how we can create a single login system that works for every part of the site -- issue tracker, mpwa, news items, and anything else we might have. I'm not familiar with WordPres or Trac setup so I don't know what options are available. I know that I personally dislike the type of login we currently have for Trac -- that browser alert box. It's ugly. I much prefer login forms on web pages, since you can make them look pretty. So... have we given any thought to how to make every part of the MacPorts web site recognize a global login?

1 0