Re: [36679] trunk/base/src — extract st age doesn't get the right tarball path

2008-05-13 Thread nox
Le 11 mai 08 à 19:14, nox a écrit : Le 11 mai 08 à 10:18, [EMAIL PROTECTED] a écrit : Revision 36679 Author [EMAIL PROTECTED] Date 2008-05-11 01:18:24 -0700 (Sun, 11 May 2008) Log Message fetch_init, archive_init, unarchive_init: Avoid creating too many subdirectory levels when these procedur

Re: [36679] trunk/base/src — extract stage doe sn't get the right tarball path

2008-05-13 Thread Joshua Root
nox wrote: jmr fixed this specific problem in r36687 and r36688, but I've found another one in the patch stage: $ sudo port install +universal ---> Fetching jpeg ---> Attempting to fetch jpegsrc.v6b.tar.gz from ftp://ftp.uu.net/graphics/jpeg ---> Attempting to fetch jpegsrc.v6b.tar.gz from

Re: [36127] trunk/base/doc/macports.conf.in

2008-05-13 Thread Ryan Schmidt
On Apr 18, 2008, at 8:46 PM, [EMAIL PROTECTED] wrote: Revision: 36127 http://trac.macosforge.org/projects/macports/changeset/36127 Author: [EMAIL PROTECTED] Date: 2008-04-18 18:46:17 -0700 (Fri, 18 Apr 2008) Log Message: --- Add comments for binpath. Modified Paths: ---

Re: [36379] trunk/base/src

2008-05-13 Thread Ryan Schmidt
On Apr 28, 2008, at 10:29 PM, [EMAIL PROTECTED] wrote: Revision: 36379 http://trac.macosforge.org/projects/macports/changeset/36379 Author: [EMAIL PROTECTED] Date: 2008-04-28 20:29:37 -0700 (Mon, 28 Apr 2008) Log Message: --- base/src: Adapting $portname @$version notat

Re: [36708] trunk/base/src/port1.0

2008-05-13 Thread Rainer Müller
[EMAIL PROTECTED] wrote: Revision: 36708 http://trac.macosforge.org/projects/macports/changeset/36708 Author: [EMAIL PROTECTED] Date: 2008-05-12 20:27:25 -0700 (Mon, 12 May 2008) Log Message: --- Allow distfiles to be disk images with new "use_dmg yes" port option; #13509

Re: [36127] trunk/base/doc/macports.conf.in

2008-05-13 Thread markd
>> +# PATH settings that are used for external tools (configure, make, >> etc.) while installing ports. The default >> +# paths are given in the example; it need not be uncommented. >> Customizing binpath is intended for advanced users only. >> +#binpath >/opt/local/bin:/opt/local/sbin:

Re: [36127] trunk/base/doc/macports.conf.in

2008-05-13 Thread Rainer Müller
[EMAIL PROTECTED] wrote: +# PATH settings that are used for external tools (configure, make, etc.) while installing ports. The default +# paths are given in the example; it need not be uncommented. Customizing binpath is intended for advanced users only. +#binpath /opt/local/bin:/opt

Re: [36127] trunk/base/doc/macports.conf.in

2008-05-13 Thread Rainer Müller
[EMAIL PROTECTED] wrote: Just use @prefix_expended@ and @x11prefix@ which will get expanded on install. We already use them at other places in this file. Are you saying that we should move where the binpath setting is set from wherever it is now to macports.conf? Also, what is @prefix_expended

Re: [36127] trunk/base/doc/macports.conf.in

2008-05-13 Thread markd
Customizing binpath is intended for advanced users only. +#binpath >>> /opt/local/bin:/opt/local/sbin:/bin:/sbin:/usr/bin:/usr/ sbin:/usr/X11R6/bin + # Directory containing the X11 installation. x11prefix@x11prefix@ >>> Shouldn't we not hard-code the pref

Re: [36127] trunk/base/doc/macports.conf.in

2008-05-13 Thread markd
>>> Just use @prefix_expended@ and @x11prefix@ which will get expanded on >>> install. We already use them at other places in this file. >> >> Are you saying that we should move where the binpath setting is set from >> wherever it is now to macports.conf? Also, what is @prefix_expended@ >> variabl

Re: [MacPorts] #15274: Warning: the following items did not execute (for macfuse): org.macports.build # (cp: invalid option -- X)

2008-05-13 Thread Kevin Ballard
On May 13, 2008, at 6:43 PM, Charles Darwin wrote: On May 13, 2008, at 7:31 PM, MacPorts wrote: #15274: Warning: the following items did not execute (for macfuse): org.macports.build # (cp: invalid option -- X) --- + Rep

Re: [ticket 15264]: need commit & requesting commit privileges

2008-05-13 Thread Rainer Müller
Adam Schenker wrote: I'd be grateful if someone could commit this for me. Also, I'd like to go ahead and request commit privileges so I don't have to keep asking on the list. I am the maintainer of the above port as well as 4 others. This should go over portmgr's desk for approval. I am CC'i

Re: octave-forge tarball format changed

2008-05-13 Thread Rainer Müller
Andrea D'Amore wrote: Hello, octave-forge portfile is pretty outdated, I got latest tarball and structure has changed, main tarball hasn't a configure script anymore,now it's only a collection of .tar.gz, each of them with its own configure script. What's the more convenient way to manage

Re: [MacPorts] #15274: Warning: the following items did not execute (for macfuse): org.macports.build # (cp: invalid option -- X)

2008-05-13 Thread Kevin Ballard
On May 13, 2008, at 6:51 PM, Charles Darwin wrote: The easiest thing for you would simply be to uninstall coreutils +with_default_names, but I assume you installed that for a reason. -Kevin Ballard That's right. And I am getting the same error when I am building from the source. 07:49:0

Re: [MacPorts] #15274: Warning: the following items did not execute (for macfuse): org.macports.build # (cp: invalid option -- X)

2008-05-13 Thread Kevin Ballard
On May 13, 2008, at 7:31 PM, Charles Darwin wrote: On May 13, 2008, at 8:05 PM, Kevin Ballard wrote: On May 13, 2008, at 6:51 PM, Charles Darwin wrote: The easiest thing for you would simply be to uninstall coreutils +with_default_names, but I assume you installed that for a reason. -Kevin

Re: [MacPorts] #15274: Warning: the following items did not execute (for macfuse): org.macports.build # (cp: invalid option -- X)

2008-05-13 Thread Kevin Ballard
On May 13, 2008, at 7:31 PM, Charles Darwin wrote: On May 13, 2008, at 8:05 PM, Kevin Ballard wrote: On May 13, 2008, at 6:51 PM, Charles Darwin wrote: The easiest thing for you would simply be to uninstall coreutils +with_default_names, but I assume you installed that for a reason. -Kevin

Re: [36748] distfiles/macfuse/macfuse-1.5.tar.bz2

2008-05-13 Thread William Siegrist
On May 13, 2008, at 9:54 PM, [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] 21:54:21 -0700 (Tue, 13 May 2008)Log Message Add dump for MacFUSE 1.5 Added Paths • distfiles/macfuse/macfuse-1.5.tar.bz2 Diff Added: distfiles/macfuse/macfuse-1.5.tar.bz2 (0 => 36748) Not sure if it really matt

Re: [36748] distfiles/macfuse/macfuse-1.5.tar.bz2

2008-05-13 Thread Kevin Ballard
On May 14, 2008, at 12:42 AM, William Siegrist wrote: On May 13, 2008, at 9:54 PM, [EMAIL PROTECTED] wrote: [EMAIL PROTECTED] 21:54:21 -0700 (Tue, 13 May 2008)Log Message Add dump for MacFUSE 1.5 Added Paths • distfiles/macfuse/macfuse-1.5.tar.bz2 Diff Added: distfiles/macfuse/macfus

Re: octave-forge tarball format changed

2008-05-13 Thread Andrea D'Amore
On 14/mag/08, at 02:04, Rainer Müller wrote: Works, but will result in a huge scripted Portfile. Each phase needs to be handwritten (fetching, extracting, etc.). Indeed I don't know about this pkg command from octave. What is its purpose? To manage octave-forge packages, it is basically