Re: svn up occasional SSL negotiation failure

and such things. Any comments? I see this all the time, from my MacPorts svn and my Ubuntu Dapper svn, especially when I'm trying to commit all those svn:eol-style and svn:keywords property changes to all the files. It doesn't seem to happen much on checkouts or updat

MD5 hash of fpconst-0.7.2.tar.gz

f between the two, which only shows minor changes in comments, but it would make packagers life easier :) We get a little anal at times and when we see a MD5 mismatch, then we're concerned about something happening to the code. Regards, Blair -- Blair Zajac, Ph.D. http://www.o

Re: Imagemagick - change x11 variant to nox11?

On Nov 27, 2006, at 10:07 PM, Mark Duling wrote: Wouldn't it make more sense for IamgeMagick to have X11 support by default and provide a nox11 for turning it off as suggested in this ticket? http://trac.macosforge.org/projects/macports/ticket/10624 +1. Blair ___

Re: No download link?

Daniel J. Luke wrote: On Dec 6, 2006, at 2:27 PM, Alexander Limi wrote: Why is there no link that makes it possible to download MacPorts anymore? http://svn.macports.org/repository/macports/downloads/ Where do I have to go to find it? It's not obvious from the http://www.macports.org page at

Re: svn:eol-style property

Regards, Blair -- Blair Zajac, Ph.D. <[EMAIL PROTECTED]> http://www.orcaware.com/svn/ ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev

Re: svn:eol-style property

Kevin Ballard wrote: Why would you care about the eol style for python files? On Jan 24, 2007, at 12:35 PM, Blair Zajac wrote: I noticed that there are Python files that you would still want a native eol-style on, and presumable other scripts. Because somebody may edit it on a non-Unix

Re: svn:eol-style property

Kevin Ballard wrote: I'm not seeing a problem right now, because all of the current patchfiles are supposed to have unix line endings. But some time ago there was a problem - a patchfile I submitted had mixed line endings, and the committer converted it to unix and added svn:eol-style, which

Re: svn:eol-style property

Kevin Ballard wrote: On Jan 25, 2007, at 3:26 AM, Randall Wood wrote: I disagree. Take it off of the */*/patch* and the 200 other patches, which I guess are poorly named then since they don't start with the word patch, and leave everything else alone. I have seen no standard that states h

Re: /Applications/DarwinPorts -> /Applications/MacPorts

Randall Wood wrote: If no one has any objections, I would like to complete the following no later than 14 Feb 2007: Change every reference to /Applications/DarwinPorts to /Applications/MacPorts in every relevant Portfile. I would like to begin working on this on 11 Feb 2007. Sounds good to

Defaulting --tclpackage to be inside of --prefix

Ports, you don't also have to find stuff in /Library or /System. So can we change the default to be something like $prefix/lib/tcl/macports? Regards, Blair -- Blair Zajac, Ph.D. <[EMAIL PROTECTED]> http://www.orcaware.com/svn/ ___ macports-

file delete -force not deleting everything

On 10.3.9, but not 10.4, the db44 port doesn't build with this error: Installing documentation: /bztmp/MacPorts/var/db/dports/build/_bztmp_MacPorts_var_db_dports_sources_rsync.rsync.darwinports.org_dpupdate_dports_databases_db44/work/destroot/bztmp/MacPorts/share/db44-4.4.20/ ... DEBUG: Execut

Re: file delete -force not deleting everything

Mike Alexander wrote: --On February 10, 2007 9:48:58 PM -0500 Kevin Ballard <[EMAIL PROTECTED]> wrote: file delete is a built-in Tcl command - do a `man n file` to see it. And yeah, it definitely should work. On Feb 10, 2007, at 8:33 PM, Blair Zajac wrote: Has anybody seen anythin

Revamping home page left sidebar

Regarding the left sidebar of links on http://www.macports.org/ I have some suggestions. The term "Source Code" is not as obvious as "Download" which people are more familiar with. We can say, we only provide source downloads, no binaries. Also, adding links to the the users, developers, t

Re: [22092] trunk/dports/python

Yves de Champlain wrote: Le 07-02-17 à 11:32, Yves de Champlain a écrit : Le 07-02-17 à 11:18, [EMAIL PROTECTED] a écrit : Revision 22092 Author [EMAIL PROTECTED] D

Re: Python 2.5 and py-crypto...

Randall Wood wrote: On 21 Feb 2007, at 20:43, Landon Fuller wrote: On Feb 21, 2007, at 15:43, Weissmann Markus wrote: Hi Douglas, the soon-to-be-released version 1.4 of port will come with a python 2.5 "port group". This will allow us to quickly produce all the python vastness for python

Re: [22092] trunk/dports/python

Jyrki Wahlstedt wrote: On 18.2.2007, at 19.39, Markus Weissmann wrote: On 18.02.2007, at 17:47, Yves de Champlain wrote: Le 07-02-17 à 14:15, Blair Zajac a écrit : Yves de Champlain wrote: Le 07-02-17 à 11:32, Yves de Champlain a écrit : Le 07-02-17 à 11:18, [EMAIL PROTECTED] <mai

Re: [22092] trunk/dports/python

Yves de Champlain wrote: Le 07-02-22 à 11:05, Blair Zajac a écrit : Jyrki Wahlstedt wrote: On 18.2.2007, at 19.39, Markus Weissmann wrote: skip ... Well, I beg to differ once again (though I am not sure it makes any difference). The ports with no version number should always be for

Re: Python 2.5 and py-crypto...

Jyrki Wahlstedt wrote: On 22.2.2007, at 5.07, Blair Zajac wrote: Randall Wood wrote: On 21 Feb 2007, at 20:43, Landon Fuller wrote: On Feb 21, 2007, at 15:43, Weissmann Markus wrote: Hi Douglas, the soon-to-be-released version 1.4 of port will come with a python 2.5 "port group&q

Re: Python 2.4 vs Python 2.5 and System vs MacPorts python

Jordan K. Hubbard wrote: This has been an interesting conversation, particularly given some of the comments from folks claiming they're facing this scenario in commercial / support scenarios where products are based on (presumably forwards incompatible) Python version x and unable to migrate to

Re: Perl still at 5.8.8?

Jordan K. Hubbard wrote: I notice we're still at Perl version 5.8.8 which is over a year old. Are we sticking at this version for a reason, or is perl 5.9.4 in the cards? The even numbers are in development versions. At some point, 5.9.x will become 5.10. Regards, Blair -- Blair

Re: [22274] trunk/dports/sysutils/file/Portfile

x27;s/^g//'`; done" } } variant normal_install_names { } A number of other packages use this name naming convention. Regards, Blair -- Blair Zajac, Ph.D. CTO, OrcaWare Technologies <[EMAIL PROTECTED]> Subversion training, consulting and support http://www.orcaware.com/svn/ O

Re: [22274] trunk/dports/sysutils/file/Portfile

You're welcome to change it. I'm not a Tcl expert my any means :) If you do change it, please change it in all the Portfiles that use this horrible code :) Just please keep 10.3 compatibility, since I still build MacPorts for 10.3. Regards, Blair -- Blair Zajac, Ph.D. CTO

Re: Default +universal variant for configure-based ports

Hi Paul, I looked through the diff for r22313 and didn't see anything that checks for OS X versions 10.3 or older, so will this break on older OSes? If it will break things, can you update the code to add this check? I support a binary install of MacPorts on a portable firewire drive that ru

Re: Default +universal variant for configure-based ports

uot; I'm presuming this is from this line in dports/textproc/libiconv/Portfile: +configure.universal_ldflags-append \ +-isysroot /Developer/SDKs/MacOSX10.4u.sdk Regards, Blair Blair Zajac wrote: Hi Paul, I looked through the diff for r22313 and didn't see anything t

Re: Default +universal variant for configure-based ports

Elias Pipping wrote: Well, i could comment it out for now - until 1.4.0 is out. Should I? that option is indeed needed for +universal to work, though. Regards, Elias Pipping On Feb 26, 2007, at 8:23 AM, Blair Zajac wrote: And do we have to wait for MacPorts 1.4.0 before using these new

Re: Default +universal variant for configure-based ports

Elias, Thanks, that does work now. Regards, Blair Elias Pipping wrote: r22321 should fix the problem. please let me know if it does/doesn't. Regards, Elias Pipping On Feb 26, 2007, at 8:34 AM, Blair Zajac wrote: That's a pretty important port, it's at the very bottom of

Re: Default +universal variant for configure-based ports

for now. I am not aware of your exact needs, but please note that MacPorts does not produce 10.3.9 PPC + 10.4 Intel universal binaries. Paul On 26 févr. 07, at 16:11, Blair Zajac wrote: Hi Paul, I looked through the diff for r22313 and didn't see anything that checks for OS X versio

Re: Default +universal variant for configure-based ports

king for support from the MacPorts community. But now that you mention this unify script from Mozilla, I'll check that out for myself :) Regards, Blair -- Blair Zajac, Ph.D. CTO, OrcaWare Technologies <[EMAIL PROTECTED]> Subversion training, consulting and

Re: Default +universal variant for configure-based ports

Paul Guyot wrote: On Feb 26, 2007, at 19:00, Blair Zajac wrote: Hello Paul, Yes, I would love to have a single Universal MacPorts build, but since I need to support 10.3, that won't be happening. But shouldn't the code adding this feature check to see if it's on 10.3 be

Re: remove p5-math-bigint port?

. So I vote to have out Perl have it's @INC reordered to have site_perl and vendor_perl first. I don't think making this change will break many things, will it? Regards, Blair -- Blair Zajac, Ph.D. CTO, OrcaWare Technologies <[EMAIL PROTECTED]> Subversion training,

Re: Default +universal variant for configure-based ports

Being somebody who actually digs into stack traces and core dumps, I would be extremely leery about loosing the -g flag. When something goes wrong, having the additional debugging information available is nice. I think there's precedence for keeping it. Most of the Linux distributions I beli

Re: gnu ports

macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev -- Blair Zajac, Ph.D. CTO, OrcaWare Technolo

Re: gnu ports

Elias Pipping wrote: The new name, without_prefix, isn't entirely accurate. I beg to differ. Would you mind reverting your variant name change and we can discuss a better name. r22390. Thanks. Any ideas? Granted normal_install_names isn't great, but it's a positive variant, in the sens

Re: gnu ports

Sounds good to me! Regards, Blair Elias Pipping wrote: +with_default_names? it's not much better but it's 'with'-conform... (like 'default' better than 'normal' for some reason) Regards, Elias Pipping On Feb 27, 2007, at 10:46 PM, Blair Zajac wro

tbz or tbz2

Have to code check for all valid types instead of trying regexps on them? Thanks, Blair -- Blair Zajac, Ph.D. CTO, OrcaWare Technologies <[EMAIL PROTECTED]> Subversion training, consulting and support http://www.orcaware.com/svn/ ___ macports-dev m

Re: MacPorts: extracting to multiple locations

new Portfile before committing it to check it out, I would appreciate it. BTW, I think we have a standard of naming beta ports with -devel and not -beta, as I can't find a single Port with the string beta in it. Regards, Blair -- Blair Zajac, Ph.D. CTO, OrcaWare Technologies <[

Re: MacPorts and Summer of Code

application ;) Best Regards, What kind of projects do you have in mind for the Summer of Code people to take on? Regards, Blair -- Blair Zajac, Ph.D. <[EMAIL PROTECTED]> Subversion training, consulting and support http://www.orcaware.c

Re: MacPorts and Summer of Code

e person who did the commit if a new Port broke on another older os. -- Blair Zajac, Ph.D. <[EMAIL PROTECTED]> Subversion training, consulting and support http://www.orcaware.com/svn/ ___ macports-dev mailing list macports-dev@lists.macosforge.org h

Re: [22479] trunk/dports/PortIndex

ax=50&daysback=90&format=rss Regards, Blair -- Blair Zajac, Ph.D. <[EMAIL PROTECTED]> Subversion training, consulting and support http://www.orcaware.com/svn/ ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.

Re: [22490] trunk/dports/www/apache2/Portfile

Hi Randall, I have a MacPorts build on a portable firewire/USB drive and on this drive is a Python app that starts Apache and MySQL and then points a browser at the local running Apache. So given that the Apache is on a portable drive, when I build the port, I don't need the startupitem, hen

Re: [22490] trunk/dports/www/apache2/Portfile

Weissmann Markus wrote: On 03.03.2007, at 10:48, Randall Wood wrote: Is this +no_startupitem variant really smart? I recently had a request to add a +without_startupitem variant to a port I maintain and rejected the request; since startupitems simply enable a port to be started at boot time,

Re: [22490] trunk/dports/www/apache2/Portfile

it isn't enabled by default. Definitely not a standard use of MacPorts, but I have a client that ships Firewire/USB drives with a MacPorts install in /Volumes/SOMENAME/. People plugin in the drive, launch a Python app which starts Apache and MySQL. Regards, Blair -- Blair Zajac

Re: One commit = one change

Ryan Schmidt wrote: Dear MacPorts committers, I've seen a lot of commits to portfiles that do more than one thing. For example, a commit that updates the port to a new version, adds a new variant, and changes the indentation of the entire file. This makes it incredibly difficult to see what a

Re: Universal ports: mozilla's unify script

I haven't found a URL to do the checkout, but this works: $ cvs -d:pserver:[EMAIL PROTECTED]:/cvsroot co mozilla/build/macosx Then look for unify. Regards, Blair Elias Pipping wrote: Could you hook me up with a link please? Regards, Elias Pipping On Mar 6, 2007, at 7:56 AM, Ryan Schmidt

Re: [22980] trunk/base/src/port1.0/resources/fetch/mirror_sites.tcl

:// access to ftp.gnupg.org precede the ftp:// access in this list? +1. Blair -- Blair Zajac, Ph.D. Subversion training, consulting and support http://www.orcaware.com/svn/ ___ macports-dev mailing list macports-dev@lists.macosforge.org http

Re: [23415] trunk/dports/archivers/zlib/Portfile

ugh. I've been using the rule that I'll wait 72 hours for my first bug/ patch to be acted upon, but if I have follow up ones on the same Portfile and there was never a response to the first report, than any successive ones I'll commit immediately. Regards, Blair -- Bl

Re: [23628] trunk/dports/lang/scala/Portfile

Elias Pipping wrote: Log Message === Tabify. Why? To prepare for my next commit. Blair ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev

Dealing with tarballs that tarbomb

The scala tarball doesn't extract into a new subdirectory and instead just extracts into the directory where you run tar, i.e. a tarbomb. So in work/, you see a bin/ and a share/ directory. Is there an easy, clean way to deal with this in MacPorts? I looked at specifying some extract options

Re: Dealing with tarballs that tarbomb

Daniel J. Luke wrote: On Apr 5, 2007, at 3:54 PM, Blair Zajac wrote: The scala tarball doesn't extract into a new subdirectory and instead just extracts into the directory where you run tar, i.e. a tarbomb. So in work/, you see a bin/ and a share/ directory. Is there an easy, clean w

Re: Dealing with tarballs that tarbomb

Eric Hall wrote: On Thu, Apr 05, 2007 at 12:54:33PM -0700, Blair Zajac wrote: The scala tarball doesn't extract into a new subdirectory and instead just extracts into the directory where you run tar, i.e. a tarbomb. So in work/, you see a bin/ and a share/ directory. Is there an easy,

Re: Dealing with tarballs that tarbomb

Elias Pipping wrote: On Apr 6, 2007, at 12:21 AM, Blair Zajac wrote: Thanks, that's what I ended up going with, however, using file mkdir ${worksrcpath} instead of the system. how about 'xinstall -d'? Don't the 'file subcommands' commands not shell o

Re: Dealing with tarballs that tarbomb

On Apr 5, 2007, at 8:20 PM, Juan Manuel Palacios wrote: On Apr 5, 2007, at 7:05 PM, Blair Zajac wrote: Elias Pipping wrote: On Apr 6, 2007, at 12:21 AM, Blair Zajac wrote: Thanks, that's what I ended up going with, however, using file mkdir ${worksrcpath} instead of the system.

Adding additional arguments to daemondo

be a way to do this in looking through portstartupitem.tcl. If there's a way to append or prepend to args, then this could be added. Any suggestions? Regards, Blair -- Blair Zajac, Ph.D. CTO, OrcaWare Technologies <[EMAIL PROTECTED]> Subversion training, consulting

Port unarchiving not working

ch com.apple.configure com.apple.build com.apple.destroot com.apple.archive com.apple.install Error: Status 1 encountered during processing. But the command doesn't contain the "bzip -d -c" I'm not a TCL expert to see why unarchive.env is being set but not ending up in the command.

Re: Port unarchiving not working

(FOO=bar FOOD=bad), whatever. This is a recent change. Does that explain the problem you're seeing? James On Apr 28, 2007, at 10:49 AM, Blair Zajac wrote: I'm trying to use the port unarchiving feature but it appears that the unarchive.env is not being honored. Here's

Re: python2.5 has wrong value for distutils.sysconfig.get_config_var("PYTHON")

ch for the python2.5 Portfile to do what you're referring to here? Regards, Blair -- Blair Zajac, Ph.D. <[EMAIL PROTECTED]> Subversion training, consulting and support http://www.orcaware.com/svn/ ___ macports-dev mailing list macports-d

Re: python2.5 has wrong value for distutils.sysconfig.get_config_var("PYTHON")

David Glasser wrote: On 5/1/07, Blair Zajac <[EMAIL PROTECTED]> wrote: Can you write a quick patch for the python2.5 Portfile to do what you're referring to here? Working on it. I've never been so good about understanding how to test my own Portfiles though --- I mean, I kno

Re: Framework Install Dir

installed to ${prefix}/Library/Frameworks. +1 on the later, as I sometimes need to make portable firewire/USB drives with a complete MacPorts build under /Volumes/something. Regards, Blair -- Blair Zajac, Ph.D. CTO, OrcaWare Technologies <[EMAIL PROTECTED]> Subversion training, consulti

Re: MacPorts v1.4.40 released for self update

sions have been merged. Regards, Blair -- Blair Zajac, Ph.D. CTO, OrcaWare Technologies <[EMAIL PROTECTED]> Subversion training, consulting and support http://www.orcaware.com/svn/ ___ macports-dev mailing list macports-dev@lists.macosforge.org http://

Re: MacPorts v1.4.40 released for self update

On May 8, 2007, at 5:52 AM, James Berry wrote: Hi Blair, On May 7, 2007, at 11:10 PM, Blair Zajac wrote: On May 7, 2007, at 9:59 PM, James Berry wrote: Here's the change log: James Release 1.4.40 (7-May-2007, tagged at r24909 by jberry): James, Thanks for pushing this releas

*.bak files in svn

Hello, In r24980, is there a reason to keep the *.bak files in Subversion? http://trac.macports.org/projects/macports/changeset/24980 Regards, Blair ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/l

Re: *.bak files in svn

ts however, so the .baks' contents might or might not become obsolete eventually - I can't tell yet. For the time being I found it reasonable to keep them; they will be removed as soon as 7.1 is out. Regards, Elias On May 10, 2007, at 12:12 AM, Blair Zajac wrote: Hello, In r24980,

Re: selfupdate is broken

Ryan Schmidt wrote: On May 10, 2007, at 09:44, Vincent Lefevre wrote: It seems that selfupdate got broken: prunille:~> sudo port -d selfupdate DEBUG: Rebuilding the MacPorts base system if needed. Synchronizing from file:///Users/vinc17/wd/macosx/dports DEBUG: /opt/local/bin/svn update --non-i

Re: selfupdate is broken

James Berry wrote: On May 10, 2007, at 7:44 AM, Vincent Lefevre wrote: It seems that selfupdate got broken: prunille:~> sudo port -d selfupdate DEBUG: Rebuilding the MacPorts base system if needed. Synchronizing from file:///Users/vinc17/wd/macosx/dports DEBUG: /opt/local/bin/svn update --non

Perl port failing

post-destroot { foreach packlist [exec find ${destroot}${perl5.lib} - name .packlist] { ui_info "Fixing packlist ${packlist}" reinplace "s|${destroot}||" ${packlist} } } Regards, Blair -- Blair Zajac, Ph.D. <[EMAIL PROTE

Re: Perl port failing

Thanks Kevin, Regards, Blair Kevin Ballard wrote: I've fixed it. I feel really stupid about that error. We need to push out a 1.4.42 now, but jmpp is idle. Hopefully he'll see my message. On May 17, 2007, at 2:32 AM, Boey Maun Suang wrote: On 17/05/2007, at 16:22, Blair Z

test.env not being evaled any more

Message --- On May 18, 2007, at 4:32 PM, Blair Zajac wrote: The tests are failing and the DYLD_LIBRARY_PATH trick isn't working, note the actual environment variable. I tried some tricks to get it working, but was unable to. Any ideas? I'm guessing base/ changed to not eval the c

Re: "mysql" port outdated?

On May 22, 2007, at 8:38 AM, James Cox wrote: On 22 May 2007, at 16:13, James Berry wrote: On May 22, 2007, at 8:09 AM, Chris Pickel wrote: There were just two people on the irc channel trying to install mysql +server. This didn't work because the mysql port depends on DarwinP

Re: GSoC2007 work

x27;s easy to keep development on a branch that may break trunk. We use it all the time at work. Regards, Blair -- Blair Zajac, Ph.D. <[EMAIL PROTECTED]> Subversion training, consulting and support http://www.orcaware.com/svn/ ___ macports-dev

Re: GSoC2007 work

Mark Grimes wrote: On 6/4/2007, "Blair Zajac" <[EMAIL PROTECTED]> wrote: Mark Grimes wrote: On 6/4/2007, "Jordan K. Hubbard" <[EMAIL PROTECTED]> wrote: On Jun 1, 2007, at 11:43 AM, Juan Manuel Palacios wrote: Again, many reasons to move GSoC work to

Re: GSoC2007 work

Jordan K. Hubbard wrote: On Jun 1, 2007, at 12:09 PM, Anant Narayanan wrote: Please do keep in mind that the students are required to submit a URL and possibly even upload code that they have authored during the summer to code.google.com at the end of the term. Committing directly to trunk pos

Re: PostgreSQL and MySQL

Ryan Schmidt wrote: On Jun 16, 2007, at 15:23, N_Ox wrote: Le 16 juin 07 à 22:06, James Berry a écrit : On Jun 16, 2007, at 7:55 AM, N_Ox wrote: For consistency's sake, wouldn't it be nicer to make mysql5 server variant its own port, as postgresql82-server port? This way, ports could even

Re: [26461] users/pipping/merge.rb

Weissmann Markus wrote: On 25 Jun 2007, at 11:37, Ryan Schmidt wrote: On Jun 25, 2007, at 03:47, Kevin Ballard wrote: On Jun 25, 2007, at 1:41 AM, Weissmann Markus wrote: Do you have any further information on unify.pl? Does it have a web page or some documentation? I wasn't aware of it nei

Re: Status of Jaguar support?

Ryan Schmidt wrote: On Jun 27, 2007, at 12:49, Eric Hall wrote: On Thu, Jun 21, 2007 at 09:31:25AM -0400, Daniel J. Luke wrote: I'm ok with keeping old Jaguar stuff in the portfiles. This desire should however be clearly communicated to all portfile authors then, mentioned in the (absent) d

Re: Release 1.5 branch created

Juan Manuel Palacios wrote: Evening everyone! I finally created the release_1_5 branch wherefrom we'll start cutting the 1.5.x releases, really soon now I hope! For those willing to help around in sanitizing, please reinstall off this branch and test as thoroughly as posible, reporti

Re: Release 1.5 branch created

On Jun 30, 2007, at 4:36 PM, Juan Manuel Palacios wrote: On Jun 30, 2007, at 12:20 PM, Blair Zajac wrote: Juan Manuel Palacios wrote: Evening everyone! I finally created the release_1_5 branch wherefrom we'll start cutting the 1.5.x releases, really soon now I hope! For

1.5.0 packaging bug

ts/packages/darwin/i386/cyrus- sasl2-2.1.21_0+kerberos darwin.i386.tbz2 " returned error 1 Command output: bzip2: Can't open input file darwin.i386.tbz2: No such file or directory. Regards, Blair -- Blair Zajac, Ph.D. <[EMAIL PROTECTED]> Subversion trainin

Re: 1.5.0 packaging & receipt bug

On Jul 15, 2007, at 6:07 PM, Blair Zajac wrote: Doing a complete rebuild of 1.5.0 today, I ran into this bug: man8/sasldblistusers2.8.gz: changing permissions from 00644 to 00444 man8/saslpasswd2.8: 51.8% -- replaced with man8/saslpasswd2.8.gz man8/saslpasswd2.8.gz: changing permissions

Re: SoC: current status (Elias Pipping)

On Jul 22, 2007, at 9:35 AM, Elias Pipping wrote: Hi, here's the status: merge.rb is a tool that's designed to merge an arbitrary amount of single-architecture directory-trees into a single universal tree. So, given the Coreutils scenario we have four directories - ppc, ppc64, i386, and x

Re: MacPorts should require the latest Xcode

On Jul 29, 2007, at 4:11 PM, Ryan Schmidt wrote: Here's a message from the -users list just now: On Jul 28, 2007, at 18:39, Chris Waterson wrote: Hey, I had the same problem. It turns out I was using an older version of Xtools (specifically, version 2.3). After upgrading to Xtools 2.4.1

Re: MacPorts should require the latest Xcode

Landon Fuller wrote: On Jul 29, 2007, at 17:21, Blair Zajac wrote: On Jul 29, 2007, at 4:11 PM, Ryan Schmidt wrote: Here's a message from the -users list just now: On Jul 28, 2007, at 18:39, Chris Waterson wrote: Hey, I had the same problem. It turns out I was using an older versi

Re: Trac tickets

work, such as: build.env 'QMAKESPEC="" QTDIR="" DYLD_LIBRARY_PATH="$ {worksrcpath}/lib"' Any ideas? I'm not going to apply the suggested change to build.cmd, since it should not be necessary. Regards, Blair -- Bl

Re: Creating self contained bundles with MacPorts

ke --with-tclpackage=/Users/Shared/OpenMacPorts/lib/tcl/macports to the configure step. I've had no issues when I do this. Regards, Blair -- Blair Zajac, Ph.D. CTO, OrcaWare Technologies <[EMAIL PROTECTED]> Subversion training, consulting and support http://www.orcaware.com/svn/ __

*.env not working

g has changed. In this case, the Portfile could set the env and the Makefile could ensure that the environment is indeed set. Another thing is to have a beefy build box that builds a large number of Portfile's before a new release and looks for any regressions in ports that used to bui

Re: *.env not working

On Aug 12, 2007, at 10:43 AM, N_Ox wrote: Le 12 août 07 à 19:02, Blair Zajac a écrit : The qt3-mac used to work with this: configure.env QMAKESPEC='' QTDIR='' DYLD_LIBRARY_PATH='' build.env QMAKESPEC='' QTDIR='' DYLD_LIBRARY_PATH

Re: MacPorts 1.5.11 (Fwd: [27780] branches/release_1_5/base)

Why are we calling it 1.5.11, I would think it would be 1.5.2, or 1.5.1.1 (not as good). Blair On Aug 14, 2007, at 1:17 AM, Juan Manuel Palacios wrote: Hello everyone! I just merged revisions r27709, r27710, r27711, r27719, r27720, r27773, r27779, comprising the latest work on mtree v

Re: MacPorts 1.5.11 (Fwd: [27780] branches/release_1_5/base)

N_Ox wrote: Le 14 août 07 à 22:01, Juan Manuel Palacios a écrit : I would say that I, human, don't recognize that .11 is less than .2 when it come to versioning. The dots are here for something, and numbers should be take separately. /me votes for 1.5.1.1! I'll go with that. But it shoul

Re: MacPorts 1.5.11 (Fwd: [27780] branches/release_1_5/base)

On Aug 14, 2007, at 6:34 PM, Ryan Schmidt wrote: On Aug 14, 2007, at 17:58, Blair Zajac wrote: N_Ox wrote: Le 14 août 07 à 22:01, Juan Manuel Palacios a écrit : I would say that I, human, don't recognize that .11 is less than . 2 when it come to versioning. The dots are her

Re: moving "macports1.0" to ${prefix}

ted prefix ? +1. I do this by hand with configure's --with-tclpackage option so I can have multiple MacPorts installed. Regards, Blair -- Blair Zajac, Ph.D. CTO, OrcaWare Technologies <[EMAIL PROTECTED]> Subversion training, consulting and support http:/

Re: moving "macports1.0" to ${prefix}

Landon Fuller wrote: On Aug 16, 2007, at 02:15, Anders F Björklund wrote: For MacPorts 1.6, it might be a good idea to consider moving "macports1.0" from the current @TCL_PACKAGE_DIR@ directory to the @prefix_expanded@/share/macports/Tcl directory, in order to make the MacPorts installatio

Re: moving "macports1.0" to ${prefix}

Landon Fuller wrote: On Aug 16, 2007, at 10:55, Blair Zajac wrote: Landon Fuller wrote: On Aug 16, 2007, at 02:15, Anders F Björklund wrote: For MacPorts 1.6, it might be a good idea to consider moving "macports1.0" from the current @TCL_PACKAGE_DIR@ directory to the @prefi

Re: moving "macports1.0" to ${prefix}

Landon Fuller wrote: On Aug 16, 2007, at 11:10, Blair Zajac wrote: Landon Fuller wrote: On Aug 16, 2007, at 10:55, Blair Zajac wrote: Landon Fuller wrote: On Aug 16, 2007, at 02:15, Anders F Björklund wrote: For MacPorts 1.6, it might be a good idea to consider moving "macports1.0&

Re: [28120] trunk/dports/lang/python24/Portfile

$prefix/Library/Framework-Python2.5 Regards, Blair -- Blair Zajac, Ph.D. <[EMAIL PROTECTED]> Subversion training, consulting and support http://www.orcaware.com/svn/ ___ macports-dev mailing list macports-dev@lists.macosforge.org http://lists.macosforge.org/mailman/listinfo/macports-dev

Re: [28120] trunk/dports/lang/python24/Portfile

Rainer Müller wrote: Boyd Waters wrote: On Aug 21, 2007, at 9:18 AM, Anders F Björklund wrote: This change will break ports that depends on "python24" and then try to use the "python" binary, either directly with #!/opt/local/bin/python or with e.g. #!/usr/bin/env python. Maybe those ports us

Re: [28120] trunk/dports/lang/python24/Portfile

Boyd Waters wrote: On Aug 21, 2007, at 11:01 AM, Blair Zajac wrote: I think we we should have separate Framework directories for each Python version, otherwise if you have 2.4 and 2.5 installed on your system, then the Current symlink will point to 2.5, presumably, and you won't be ab

Re: [28120] trunk/dports/lang/python24/Portfile

Boyd Waters wrote: On Aug 21, 2007, at 9:18 AM, Anders F Björklund wrote: This change will break ports that depends on "python24" and then try to use the "python" binary, either directly with #!/opt/local/bin/python or with e.g. #!/usr/bin/env python. Maybe those ports using port:python24 s

Re: Default compiler suite (was Re:[28325] trunk/dports/graphics/wxWidgets-devel/Portfile)

to the configure.env and build.env not honoring it. If somebody could fix MacPorts (and not the Portfile) to honor it, I would appreciate it. See this ticket for information on when the *.env broke: http://trac.macports.org/projects/macports/ticket/11895 Regards, Blair -- Blair Zajac,

Re: daemondo defeats purpose of launchd?

[EMAIL PROTECTED] wrote: Ryan Schmidt <[EMAIL PROTECTED]> writes: Agreed. I try to avoid daemondo when possible. When it isn't possible, daemondo is an indispensable tool, but it turns out that for most cases, it's possible to avoid it. I've written many launchd scripts on my own, several o

Re: PLEASE READ: Whitespace rules

arate changeset to keep the svn history and diffs clean. I recommend everybody do this. The thing we edit the most here is Portfile's, so I would suggest changing all the SHOULD's for Portfile's to MUST's, as that's where I'd like to see the most standardization. R

Re: PLEASE READ: Whitespace rules

Simon Ruderich wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA512 Kevin Ballard wrote: Last time this was brought up only one person complained, but it really is a serious problem and we need standards. Therefore I propose the following: If I remember correctly, last time was decided ever

  1   2   3   4   5   6   >