February 2008 - macports-dev - lists.macosforge.org

Re: [33738] trunk/dports/databases/postgresql83
by Ryan Schmidt 04 Feb '08

04 Feb '08

On Feb 4, 2008, at 07:08, mww(a)macports.org wrote: > -#livecheck.check regex > -#livecheck.url ${homepage} > -#livecheck.regex v(8.3.\[0-9\]+) > -livecheck.check regex > -livecheck.url http://www.postgresql.org/ftp/source/ > -livecheck.regex v(8.3RC\[2-9\]) > +livecheck.check regex > +livecheck.url ${homepage} > +livecheck.regex v(8.3.\[0-9\]+) The livecheck regex isn't really accurate... you want: livecheck.regex v(8\\.3\\.\[0-9\]+)

1 0

Updated Portfile for 'lang/slime' attached to ticket 14136
by Mark Evenson 04 Feb '08

04 Feb '08

As maintainer of the 'lang/slime' port I have created an essentially reworked Portfile attached to ticket [14136][1] which: * updates the SLIME sources to CVS HEAD of 20080203, which reflects the major refactoring into a 'contrib' subdirectory that occured in the last couple of months * now has an 'app' variant that will install with the 'emacs-app' port (thanks to Jamison Hope for the initial patch) * removed the obsolescent 'devel' variant ('emacs-devel' is no longer in the MacPorts trunk * updated style to comply with what is outlined in http://guide.macports.org/#development.practices (no tabs, 4 column indents, Emacs/vim initial modeline) * rewrote the sample '.emacs' initialization code message to conform with the new style enabling SLIME to more easily serve as the frontend to multiple Lisp (or with varying commandline options) [1]: http://trac.macosforge.org/projects/macports/ticket/14136 Could someone please commit the Portfile? Mark <evenson(a)panix.com> (who is a maintainer, but doesn't have commit rights, even though he is subscribed to the very chatty macports-change list, and is marked as the maintainer of 'lang/slime' and 'lang/nxml-mode', and wouldn't mind terribly if somebody wanted to change that situation).

1 0

Re: [33397] trunk/dports/gnome/inkscape/Portfile
by Adam Mercer 04 Feb '08

04 Feb '08

On Jan 26, 2008 3:04 AM, <gui_dos(a)macports.org> wrote: > Revision 33397 Author gui_dos(a)macports.org Date 2008-01-26 00:03:38 -0800 > (Sat, 26 Jan 2008) > Log Message Comment out the dependency on py25-numpy because > the compilation of the whole gcc42 is required at > the moment linking with g95 has been fixed so it is again the default fortran compiler for py25-numpy Cheers Adam

1 0

Not installed as an image?
by Randall Wood 03 Feb '08

03 Feb '08

Given this Portfile (its also attached): =========================== # $Id: Portfile 33667 2008-02-02 20:26:04Z rhwood(a)macports.org $ PortSystem 1.0 name transmission-x11 version 1.04 revision 0 categories net gnome x11 maintainers nomaintainer description Lightweight BitTorrent client long_description Transmission is a free, lightweight BitTorrent client. \ It features a simple, intuitive interface on top of an \ efficient, cross-platform back-end. Transmission is open \ source (MIT license) and runs on Mac OS X (Cocoa interface), \ Linux/NetBSD/FreeBSD/OpenBSD (GTK+ interface) and BeOS \ (native interface). \n\n\ This is the GTK+ version. homepage http://www.transmissionbt.com/ master_sites http://download.m0k.org/transmission/files/ distname transmission-${version} checksums md5 7234c2e7c9855ea62768f89196f5913f use_bzip2 yes platforms darwin freebsd depends_lib port:gettext port:gtk =========================== why am I getting this error: =========================== Getafix:transmission-x11 rhwood$ sudo port install Password: ---> Fetching transmission-x11 ---> Attempting to fetch transmission-1.04.tar.bz2 from http://download.m0k.org/transmission/files/ ---> Verifying checksum(s) for transmission-x11 ---> Extracting transmission-x11 ---> Configuring transmission-x11 ---> Building transmission-x11 with target all ---> Staging transmission-x11 into destroot ---> Installing transmission-x11 1.04_0 ---> Activating transmission-x11 1.04_0 Error: Target org.macports.activate returned: Image error: transmission-x11 @1.04_0 not installed as an image. Error: Status 1 encountered during processing. =========================== macports.conf on my system has used the image install type since whenever I began using darwinports way back when. My machine: =========================== Getafix:transmission-x11 rhwood$ port version Version: 1.600 Getafix:transmission-x11 rhwood$ uname -v Darwin Kernel Version 9.1.0: Wed Oct 31 17:48:21 PDT 2007; root: xnu-1228.0.2~1/RELEASE_PPC =========================== Complete -dv log output is attached. -- 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

Re: [MacPorts] #14147: port lint should warn on illegal variant names
by Rainer Müller 02 Feb '08

02 Feb '08

MacPorts wrote: > #14147: port lint should warn on illegal variant names > -------------------------------------+-------------------------------------- > Reporter: ryandesign(a)macports.org | Owner: macports-tickets(a)lists.macosforge.org > Type: enhancement | Status: new > Priority: Normal | Milestone: MacPorts base enhancements > Component: ports | Version: 1.7.0 > Keywords: | > -------------------------------------+-------------------------------------- > `port lint` should warn when it encounters variants whose names are not > composed entirely of legal characters. I'm not sure if the list of legal > characters for variant names has ever been defined anywhere before, but > looking through all variant names of all ports right now, I see that they > are all composed of letters A-Z and a-z, numbers 0-9, underscore and > hyphen/dash, and the hyphen/dash is the only one of those that causes > problems. (A variant with a hyphen/dash in the name cannot be selected.) > So `port lint` should warn if a variant name does not match the regular > expression `^[A-Za-z0-9_]+$` > > Related: the guide should say something about valid variant names; see > #14141. In ''proc variant'' itself are no checks at all, the first argument ("provides") is taken as the variant name (see port1.0/portutil.tcl, proc variant {args}). But in other places there are checks for validity. port1.0/portutil.tcl, handle_default_variants: if {[regexp {([-+])([-A-Za-z0-9_]+)} $v whole val variant]} { port/port.tcl, split_variants: set l [regexp -all -inline -- {([-+])([[:alpha:]_]+[\w\.]*)} $variants] If there should be no hyphens/dashes in variant names, the regex in the ticket is correct and the one in handle_default_variants is wrong. I am unsure if I understand the regex in split_variants correctly... Maybe they should be unified to a single regex for variant names which can be used in multiple places. Rainer

1 0

macports-users has been fixed
by William Siegrist 02 Feb '08

02 Feb '08

Sorry for the oversight, there was a mis-set permission on the server for macports-users. All the mail got deferred and has now been delivered. -Bill ---- William Siegrist Software Support Engineer Mac OS Forge http://macosforge.org/ wsiegrist(a)apple.com 408 862 7337

1 0

macports-users list dead?
by Bryan Blackburn 02 Feb '08

02 Feb '08

I haven't seen any mail on macports-users since the 29th of January; also, the archives[1] appear to stop at that same day, so I don't think it's an issue with my delivery alone. Bryan [1] - <http://lists.macosforge.org/pipermail/macports-users/>

2 1

Re: [33653] trunk/dports/net/psi/Portfile
by Ryan Schmidt 02 Feb '08

02 Feb '08

Looks like you didn't commit the patchfiles. $ sudo port checksum psi +plugins ---> Fetching psi ---> Attempting to fetch patch-src_about.ui from http:// svn.macports.org/repository/macports/distfiles/psi ---> Attempting to fetch patch-src_about.ui from http:// svn.macports.org/repository/macports/distfiles/general/ ---> Attempting to fetch patch-src_about.ui from http:// svn.macports.org/repository/macports/downloads/psi Error: Target org.macports.fetch returned: fetch failed Error: Status 1 encountered during processing. $ Also, the patchfile names aren't up to code. $ sudo port lint psi +plugins ---> Verifying Portfile for psi Warning: Line 4 should be a newline (after PortSystem) Warning: Patchfile patch-src_about.ui does not follow the source patch naming policy "patch-*.diff" Warning: Patchfile patch-src_psiaccount.cpp does not follow the source patch naming policy "patch-*.diff" Warning: Patchfile patch-src_pluginmanager.cpp does not follow the source patch naming policy "patch-*.diff" Warning: Patchfile patch-src_psiplugin.h does not follow the source patch naming policy "patch-*.diff" Warning: Patchfile patch-src_pluginmanager.h does not follow the source patch naming policy "patch-*.diff" Warning: Patchfile patch-configure does not follow the source patch naming policy "patch-*.diff" ---> 0 errors and 7 warnings found. $ On Feb 2, 2008, at 10:01, rowue(a)macports.org wrote: > Revision: 33653 > http://trac.macosforge.org/projects/macports/changeset/33653 > Author: rowue(a)macports.org > Date: 2008-02-02 08:01:42 -0800 (Sat, 02 Feb 2008) > > Log Message: > ----------- > Added variant bundledqca for use of bundled qca and > variant plugins for use of experimental plugin feature > > Modified Paths: > -------------- > trunk/dports/net/psi/Portfile > > Modified: trunk/dports/net/psi/Portfile > =================================================================== > --- trunk/dports/net/psi/Portfile 2008-02-02 15:42:56 UTC (rev 33652) > +++ trunk/dports/net/psi/Portfile 2008-02-02 16:01:42 UTC (rev 33653) [snip] > +variant plugins description {Build with experimental Plugin > Support} { > + > +patchfiles-append patch-src_about.ui \ > + patch-src_psiaccount.cpp \ > + patch-src_pluginmanager.cpp \ > + patch-src_psiplugin.h \ > + patch-src_pluginmanager.h \ > + patch-configure > + > +configure.args-append --enable-plugins > +}

1 0

Re: [33639] branches/release_1_6/base/portmgr/dmg/postflight
by Juan Manuel Palacios 02 Feb '08

02 Feb '08

On Feb 2, 2008, at 2:46 AM, jmpp(a)macports.org wrote: > Revision > 33639 > Author > jmpp(a)macports.org > Date > 2008-02-01 23:16:35 -0800 (Fri, 01 Feb 2008) > Log Message > > * Use dscl(1) to detect the default shell for the installing user, > rather than trying to infer it from the inherited environment > (which did not reflect the user's at all, as it is entirely > imposed by Installer.app when the pkg is used in real life). Thanks > to Ryan on macports-dev for the original suggestion! > > * Provide a little more information about the shell we detected. > > NOTE: I tested this edited script through a test pkg on Leopard and > it works, both when used from an account with a bash shell and > from one with a tcsh shell. If anyone cares to test on Tiger and/or > Panther, they should contact me so I can hand them the pkg, thanks! > In any case, I'm feeling confident it'll work consistently this time > round to detect the shell type, given the nature of the dscl > operation. As you can see from the diff in this commit, I used an alternate method to get the sole shell name (awk). But in any case, the all work and produce the same output, as discussed on IRC earlier today, it's only a matter of taste. I've put together a test dmg that has the latest /branches/ release_1_6/base/portmgr/dmg/postflight in it, available at the following URL: http://apollo.homeunix.net/macports/downloads/MacPorts-1.6.1.dmg Appreciate it if anyone has a chance to help me test it, per my commit log above. Tiger and Panther reports would be great! Regards,... -jmpp PS: Note that the MacPorts code in the installer is not necessarily what 1.6.1 final will be, I exported a tarball off the branch some days ago (so it's definitely not current wrt trunk and may even not be current wrt the branch itself. I'm only interested here in the behavior of the postflight script when run from within Installer.app (which is what was crippling the $SHELL evn variable detection).

1 0

how to commit ...
by John Owens 02 Feb '08

02 Feb '08

OK, hate to admit this, but I'm ready to make a change to a portfile and, with the permission of the port maintainer, am ready to check into svn. But I don't know how, and I can't find any docs on macports.org on how to do this. I've used svn before ... What is the server? (svn.macports.org?) What is the path (just /trunk/...)? Log in with my macports id? username or username(a)macports.org? Is there any way to do this without having to check out a working copy (I'd rather just change a Portfile and the Portindex locally, check it works, and then check in the Portfile back into trunk)? Good doc to have on the wiki. JDO

2 3