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

Re: [32086] trunk/dports/aqua/emacs-app/Portfile
by Ryan Schmidt 17 Dec '07

17 Dec '07

On Dec 16, 2007, at 11:56, css(a)macports.org wrote: > -# http://sourceforge.net/tracker/index.php? > func=detail&aid=1810588&group_id=148174&atid=770756 > -patchfiles 20071015_rc2a.patch Should this patchfile also be removed from the files directory then?

2 1

Re: [32084] trunk/dports/devel/codeblocks-devel/Portfile
by Ryan Schmidt 16 Dec '07

16 Dec '07

On Dec 16, 2007, at 07:31, afb(a)macports.org wrote: > Log Message: > ----------- > fixed bug with GetMessageManager (upstream r4737) > > Modified Paths: > -------------- > trunk/dports/devel/codeblocks-devel/Portfile > > Modified: trunk/dports/devel/codeblocks-devel/Portfile > =================================================================== > --- trunk/dports/devel/codeblocks-devel/Portfile 2007-12-16 > 12:02:58 UTC (rev 32083) > +++ trunk/dports/devel/codeblocks-devel/Portfile 2007-12-16 > 13:31:20 UTC (rev 32084) > @@ -19,7 +19,7 @@ > > fetch.type svn > svn.url svn://svn.berlios.de/codeblocks/trunk > -#svn.tag 4365 > +#svn.tag 4737 > worksrcdir trunk > > # autoconf >= 2.50, automake >= 1.9, libtool >= 1.4 Does changing a commented line really change anything in the port?

2 1

merge for universal builds (was: Re: [31954] trunk/base/src/port1.0/portutil.tcl)
by Ryan Schmidt 16 Dec '07

16 Dec '07

On Dec 12, 2007, at 11:50, mww(a)macports.org wrote: > Revision: 31954 > http://trac.macosforge.org/projects/macports/changeset/31954 > Author: mww(a)macports.org > Date: 2007-12-12 09:50:49 -0800 (Wed, 12 Dec 2007) > > Log Message: > ----------- > add 'merge' function for mergin multiple (single arch) destroots > into one (universal) destroot How does this compare with http://trac.macports.org/projects/macports/browser/users/pipping/ merge.rb and how does it relate to backup() and lipo() in http://trac.macports.org/projects/macports/browser/trunk/base/src/ port1.0/portutil.tcl ?

3 6

Re: [31844] trunk/dports/x11/gtk2/Portfile
by Weissmann Markus 16 Dec '07

16 Dec '07

Hmmm... wouldn't it be much cleaner and easier to only have one variant "quartz" as "quartz" and "x11" are mutually exclusive anyway? This way it wouldn't be necessary to explain to a user why the selection "x11 and quartz" he just made is illegal. Regards, -Markus On 10.12.2007, at 01:54, ryandesign(a)macports.org wrote: > Revision 31844 Author ryandesign(a)macports.org Date 2007-12-09 > 16:54:17 -0800 (Sun, 09 Dec 2007) Log Messagegtk2: make +x11 the > default only if +quartz has not been selected. If you want both, > you can still request +x11 +quartzModified Paths > trunk/dports/x11/gtk2/Portfile > Diff > Modified: trunk/dports/x11/gtk2/Portfile (31843 => 31844)--- trunk/ > dports/x11/gtk2/Portfile 2007-12-10 00:53:23 UTC (rev 31843) +++ > trunk/dports/x11/gtk2/Portfile 2007-12-10 00:54:17 UTC (rev 31844) > @@ -49,7 +49,9 @@ port:render \ port:zlib -default_variants +x11 > +if { ![variant_isset quartz] } { + default_variants +x11 +} pre- > fetch { if { ![variant_isset quartz] && ![variant_isset x11] } { @@ > -88,7 +90,7 @@ configure.args-append --with-gdktarget=quartz } - > variant x11 description {Enable rendering in X11} { +variant x11 > description {Enable rendering in X11 (default, if Quartz is not > enabled)} { depends_lib-append \ port:xrender \ lib:libX11.6:xorg > _______________________________________________ > macports-changes mailing list > macports-changes(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-changes --- Dipl. Inf. (FH) Markus W. Weissmann http://www.mweissmann.de/ http://www.macports.org/

3 6

Re: [32020] trunk/dports/devel/libssh2/Portfile
by Ryan Schmidt 16 Dec '07

16 Dec '07

On Dec 13, 2007, at 13:52, pmq(a)macports.org wrote: > - > -patchfiles libssh2-0.17-banner-wait.diff > -patch.args -p1 > - Should the libssh2-0.17-banner-wait.diff file also be removed from the files directory, since it appears no longer to be referenced?

2 1

tcl-nap
by Takeshi Enomoto 16 Dec '07

16 Dec '07

I created a Portfile for tcl-nap, a Tcl extension to process n-dimensional arrays. I also created a ticket for HDF4, a scientific file format required by tcl-nap. Takeshi http://trac.macosforge.org/projects/macports/ticket/13603 http://trac.macosforge.org/projects/macports/ticket/13605

1 0

Proper way to submit a Portfile?
by Simon Bjorklen 16 Dec '07

16 Dec '07

Hi, A couple of weeks ago I submitted a port, incl patches, to the trac system. However, since it still shows up as 'new', what's the proper way to make the submit? The portfile has Ticket # 13465. Regards, Simon Björklén

2 1

Objection to wikifying the guide
by markd＠macports.org 15 Dec '07

15 Dec '07

I am going out of town tomorrow and I may not be able to participate fully in this conversation until three weeks hence, but I feel the need to set a discussion that has begun privately before the community. I think that major changes to the guide, should be done only after the doc team has properly considered it. simon@ has been and is doing major changes, but we have been coordinating together on major commits and I think we are on the same page as far as goals. I rewrote the guide from scratch for a reason, and I also think a consensus was reached that the guide would be better served by XML/DocBook rather than a wiki mainly because editorial control was exercised over it so a consistent vision would be enforced throughout (other important benefits were I think tangential). But there is a use for wikis nonetheless, and I thought we'd still be using one. The guide cannot be all things to all people, or it might as well be on a wiki. I don't think any particular text string "should be in the guide", any more than an iPod must have an integrated FM tuner. Adding text for various individual purposes to meet individual goals without consideration for the overall purpose of the guide will result over time in a guide that pleases no one. I do not think that portmgr@ requests for specific changes to the guide trump the editorial control of the doc team. Aside from the question of editorial control, I object to the following practices without a decent argument. - adding new technical terms without a value to our target audience - fragmenting it (or parts of it) into explicit "advanced/non-advanced" titles unnecessarily - explicitly referencing version numbers unneccessarily in the guide, be it MacPorts, Mac OS X, or any other The frequent argument that this or that text string "needs to be somewhere" is not adequate because "somewhere" should not automatically mean the guide. The guide was meant to be one of our documents, but not the only one. Besides which, as a MacPorts member, I reserve the right to argue for changing the terms, script names, etc. that the portmgr@ team has used for MP base and installer code to harmonize them with plans for the guide. I intend to argue for at one such change to MP base for this reason in January. Error message (and other terms introduced by code) consistency with other elements of a project is a hallmark of the difference between a Mac and Windows. This is not a question of being territorial, but a question of principle. I didn't state the principles I was operating on clearly upfront (other than to call it a "minimalist guide") because I was the sole author at the time. But I think the user experience of accessing the guide is very important, so that what is communicated and how should be closely controlled. Pick up an Apple manual and compare it to Dell's docs. I'm not saying the guide meets that standard, but we're trying to lay the groundwork so far as it is possible given the nature of the project, and we'll definitely fail without strictly adhering to some principles. I had hoped to put off requiring patches in Trac for guide changes until the guide was "feature complete", but I'll gladly do that, and adhere to it myself, rather than see the guide wikified by requests from portmgr@ that aren't in keeping with the original design goals of the guide. I want to see, and offer, competing visions of major guide additions (when available) before they are committed. I'll have to submit my competing vision for the changes required by MP 1.6 in early January after the fact. Mark

2 1

Default ticket ownership
by Juan Manuel Palacios 15 Dec '07

15 Dec '07

So, thanks again to Bill working hard to make our stay on Mac OS Forge a pleasant one, the macports-tickets list has been added to the list of ticket assignees on Trac (which was harder that it sounds!) and has also been made default owner for "base", "ports" and "www" tickets. That means that all new tickets against any of those components will be owned by that list by default, if not otherwise stated (the "guide" component is still assigned to Mark Duling by default, speak up if you feel this should be changed ;-). Also, all tickets that fell under macports-dev parenthood while macports-tickets was disabled have been updated to be children of macports-tickets (as they should have always been), which basically means two things: 1) we wont be getting any more Trac mail on this list, woot! 2) there's no longer any macports-dev in Trac's db, so any custom queries there are should be updated to reflect this; let me know if there's anything that requires admin perms for tweaking. Regards,... -jmpp

2 1

Re: [32055] trunk/dports/fuse
by Yamamoto Takanori 15 Dec '07

15 Dec '07

> In the future, please don't make changes to my Portfiles without telling me Before committing this change I certainly opened Ticket #13185 and cc'd you. So I guess you probably overlooked my mail. Anyway, sorry if I made you feel bad. On Dec 15, 2007, at 4:01 AM, eridius(a)macports.org wrote: > Revision > 32055 > Author > eridius(a)macports.org > Date > 2007-12-14 11:01:31 -0800 (Fri, 14 Dec 2007) > Log Message > > Fix the message takanori made of my MacFUSE portfiles. > In the future, please don't make changes to my Portfiles without > telling me > Modified Paths > > trunk/dports/fuse/fusefs/Portfile > trunk/dports/fuse/libfuse/Portfile > trunk/dports/fuse/sshfs/Portfile > Diff > > Modified: trunk/dports/fuse/fusefs/Portfile (32054 => 32055) > --- trunk/dports/fuse/fusefs/Portfile 2007-12-14 19:00:02 UTC (rev > 32054) > +++ trunk/dports/fuse/fusefs/Portfile 2007-12-14 19:01:31 UTC (rev > 32055) > @@ -5,7 +5,7 @@ > > name fusefs > version 1.1 > -revision 2 > +revision 3 > categories fuse devel > platforms darwin > maintainers eridius(a)macports.org > @@ -19,21 +19,14 @@ > > homepage http://code.google.com/p/macfuse/ > master_sites macports > -distname macfuse-${version} > -checksums md5 42487d7684b1f9a8eb2f8a61b10f7913 \ > - sha1 6347e5b6b0f810a3e5b0fbc82cbccfdf3f4c6311 > +distname fusefs-${version} > +worksrcdir fusefs > +checksums md5 e34f44bcbb43a370a0ef204054276ae4 \ > + sha1 776a7cf88c82bf63a8f086f086d06fb08a60c860 > > -platform darwin 8 {} > +livecheck.distname MacFUSE-Core-(.*).dmg > +livecheck.version 10.5-${version}.1 > > -if {[variant_isset darwin_8]} { > - set product_version 10.4 > -} else { > - set product_version 10.5 > -} > - > -worksrcdir ${distname}/core/${product_version}/${name} > -livecheck.distname MacFUSE-Core-${product_version}-(.*).dmg > - > use_bzip2 yes > > destroot.violate_mtree yes > @@ -42,17 +35,18 @@ > xcode.target fusefs load_fusefs fusefs.fs mount_fusefs > xcode.build.settings OBJROOT=build/ SYMROOT=build/ > > -# ensure that user is running OS X 10.4 > +platform darwin 8 { > + worksrcdir fusefs/10.4 > +} > + > +platform darwin 9 { > + worksrcdir fusefs/10.5 > +} > + > +# ensure that user is running OS X 10.4 or higher > pre-fetch { > - if {${os.platform} == "darwin"} { > - set vers [split [exec sw_vers -productVersion] .] > - set majorVersion [lindex $vers 0] > - set minorVersion [lindex $vers 1] > - if {"$majorVersion.$minorVersion" < 10.4} { > - return -code error "MacFUSE requires at least Mac OS X > 10.4 to run" > - } > - } else { > - return -code error "MacFUSE is for Mac OS X only" > + if {![variant_isset darwin_8] && ![variant_isset darwin_9]} { > + return -code error "MacFUSE requires at least Mac OS X 10.4 > to run" > } > } > > @@ -85,6 +79,11 @@ > fs-traverse file [list ${macfuse_bundle_dir}] { > file attributes $file -owner root -group wheel > } > + > + # copy header files that libfuse needs > + foreach file [list fuse_ioctl.h fuse_mount.h fuse_param.h > fuse_version.h] { > + file copy -- ${worksrcpath}/common/${file} ${destroot}$ > {prefix}/include/${file} > + } > } > > post-activate { > Modified: trunk/dports/fuse/libfuse/Portfile (32054 => 32055) > --- trunk/dports/fuse/libfuse/Portfile 2007-12-14 19:00:02 UTC (rev > 32054) > +++ trunk/dports/fuse/libfuse/Portfile 2007-12-14 19:01:31 UTC (rev > 32055) > @@ -4,8 +4,7 @@ > > name libfuse > version 2.7.1 > -revision 2 > -set macfuse_version 1.1 > +revision 3 > categories fuse devel > platforms darwin > maintainers eridius(a)macports.org > @@ -14,46 +13,74 @@ > > homepage http://fuse.sourceforge.net/ > > -master_sites macports:fusefs > -distname macfuse-${macfuse_version} > -dist_subdir fusefs > -checksums md5 42487d7684b1f9a8eb2f8a61b10f7913 \ > - sha1 6347e5b6b0f810a3e5b0fbc82cbccfdf3f4c6311 > +distname fuse-${version} > +master_sites sourceforge:fuse > +checksums ${distfiles} md5 > f95b4a238a3df5a92e9013ecb55c2c17 \ > + sha1 > ea28a61ff63cd0cf12cd7c9c092a57d79c12edf8 > > -platform darwin 8 {} > +livecheck.distname fuse-2.X > > -if {[variant_isset darwin_8]} { > - set product_version 10.4 > -} else { > - set product_version 10.5 > +depends_lib port:pkgconfig > + > +platform darwin { > + depends_run port:fusefs > + if {[variant_isset darwin_8]} { > + patch_sites http://macfuse.googlecode.com/svn/tags/macfuse-1.1/core/10.4/libfuse/ > + checksums-append fuse-2.7.1-macosx.patch md5 > 36b116114c04f8e7c65a5c8aad753573 \ > + sha1 > 5cb3440a73b2634e18f76263c35044e58b0daaa5 > + } else { > + patch_sites http://macfuse.googlecode.com/svn/tags/macfuse-1.1/core/10.5/libfuse/ > + checksums-append fuse-2.7.1-macosx.patch md5 > 85f1654ae01064ef1c398dbfde1a3f53 \ > + sha1 > 24d735331ec897c77e19203d3d38ab55ae56f292 > + > + } > + patchfiles fuse-2.7.1-macosx.patch > + > + configure.post_args-append CFLAGS="-D__FreeBSD__=10 - > D_POSIX_C_SOURCE=200112L" > + > + # override patch.pre_args since it defaults to -p0 > + patch.pre_args -p1 > } > > -worksrcdir ${distname}/core/${product_version}/${name}/ > fuse-${version} > - > -#livecheck.distname fuse-2.X > - > -use_bzip2 yes > - > -depends_lib port:pkgconfig > -depends_run port:fusefs > - > pre-fetch { > # LibFUSE currently only works on OS X > # so error out if attempting to install elsewhere > - if {${os.platform} != "darwin"} { > + if {![variant_isset darwin]} { > return -code error "LibFUSE is only supported for Mac OS X" > } > + > + if {[variant_isset darwin]} { > + patch_checksum > + } > } > > -post-extract { > - system "cd ${workpath}/${distname}/core/${product_version}/$ > {name} && gzip -dc fuse-current.tar.gz | tar --no-same-owner -xf -" > - system "cd ${worksrcpath} && patch -p1 < ../fuse-current- > macosx.patch" > -} > - > -patch { > - reinplace "s|--prefix=/usr/local|--prefix=${prefix}|" $ > {worksrcpath}/darwin_configure.sh > -} > - > -configure { > - system "cd ${worksrcpath} && /bin/sh ./darwin_configure.sh $ > {workpath}/${distname}/core/${product_version}/fusefs" > -} > +proc patch_checksum {} { > + global checksums_array UI_PREFIX > + # assume we only have one patchfile, because at the moment > that's true > + set patchfile [option patchfiles] > + # do our own checksumming of an existing $patchfile because URL > changes between revisions > + # if the checksum fails, delete the patchfile > + # a lot of this code is copied from checksum_main > + # Eventually this technique should be replaced with a patchfile > dist subdir > + if {[file exists [option distpath]/$patchfile]} { > + ui_info "$UI_PREFIX $patchfile exists, checksumming to > detect URL change" > + if {[parse_checksums [option checksums]] == "yes"} { > + ui_info "$UI_PREFIX [format [msgcat::mc "Checksumming > %s"] $patchfile]" > + set fullpath [file join [option distpath] $patchfile] > + if {[info exists checksums_array($patchfile)]} { > + set checksums $checksums_array($patchfile) > + > + foreach {type sum} $checksums { > + set calculated_sum [calc_$type $fullpath] > + if {![string equal $sum $calculated_sum]} { > + ui_debug "Checksum mismatch for $patchfile" > + delete $fullpath > + break > + } > + } > + } > + } else { > + return -code error "Unable to parse checksum string" > + } > + } > +} > \ No newline at end of file > Modified: trunk/dports/fuse/sshfs/Portfile (32054 => 32055) > --- trunk/dports/fuse/sshfs/Portfile 2007-12-14 19:00:02 UTC (rev > 32054) > +++ trunk/dports/fuse/sshfs/Portfile 2007-12-14 19:01:31 UTC (rev > 32055) > @@ -5,7 +5,6 @@ > name sshfs > version 1.8 > revision 2 > -set macfuse_version 1.1 > categories fuse > platforms darwin > maintainers eridius(a)macports.org > @@ -39,7 +38,7 @@ > > platform darwin { > depends_run port:fusefs > - patch_sites http://macfuse.googlecode.com/svn/tags/macfuse-$ > {macfuse_version}/filesystems/sshfs > + patch_sites http://macfuse.googlecode.com/svn/tags/macfuse-1.1/filesystems/sshfs > patchfiles sshfs-fuse-${version}-macosx.patch > checksums-append sshfs-fuse-${version}-macosx.patch md5 > 5d3cec641c22e89dd840c6bbc3af89d4 \ > sha1 > 79f058e0ae4b90ec09d50ab39401773d146bdf95 > _______________________________________________ > macports-changes mailing list > macports-changes(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-changes

4 3