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

Re: [26535] trunk/doc/faq/Makefile
by Juan Manuel Palacios 28 Jun '07

28 Jun '07

Hey Daniel! In my break-down of guide vs. wiki documentation in one of my posts just yesterday, one thing I forgot to mention is that I believe a fluent and up to date FAQ is more appropriate for the Wiki rather than a naturally slower docbook based solution[1]. In fact I think there's already a FAQ wiki doc, so maybe we could look at integrating these two into a single doc up there and leaving these sources behind...? Regards,... -jmpp [1] A FAQ that is in any way stale makes no sense at all, so being able to update it on the fly is much more of a *MUST* for the FAQ than for the guide. For one, more people can get to the Wiki quicker and easier, which in my opinion more than justifies the move. On Jun 27, 2007, at 7:27 PM, source_changes(a)macosforge.org wrote: > Revision > 26535 > Author > dluke(a)macports.org > Date > 2007-06-27 16:27:21 -0700 (Wed, 27 Jun 2007) > Log Message > > s/dports/macports/ > Modified Paths > > trunk/doc/faq/Makefile > Diff > > Modified: trunk/doc/faq/Makefile (26534 => 26535) > --- trunk/doc/faq/Makefile 2007-06-27 23:14:05 UTC (rev 26534) > +++ trunk/doc/faq/Makefile 2007-06-27 23:27:21 UTC (rev 26535) > @@ -73,4 +73,4 @@ > clean: > rm -fr ${HTMLDIR} ${XHTMLDIR} > > -include ../../base/Mk/dports.autoconf.mk > +include ../../base/Mk/macports.autoconf.mk > _______________________________________________ > macports-changes mailing list > macports-changes(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-changes

2 1

Re: [26536] trunk/base/src
by Juan Manuel Palacios 28 Jun '07

28 Jun '07

Hi Anders! I know you told me this new target is still experimental, but I went ahead and hooked it up for real usage in r26543... I mean, what better way to test something than by actually using it? ;-) Could you please provide some documentation for it both in the ChangeLog (base/ChangeLog) and in the port(1) man page (base/src/port/ port.1)? Keep up the effort and good work! Regards,... -jmpp On Jun 27, 2007, at 7:45 PM, source_changes(a)macosforge.org wrote: > Revision > 26536 > Author > afb(a)macports.org > Date > 2007-06-27 16:45:18 -0700 (Wed, 27 Jun 2007) > Log Message > > experimental target to build SRPM (source RPM) > Modified Paths > > trunk/base/src/package1.0/package.tcl > trunk/base/src/port1.0/portutil.tcl > Added Paths > > trunk/base/src/package1.0/portsrpm.tcl > Diff > > Modified: trunk/base/src/package1.0/package.tcl (26535 => 26536) > --- trunk/base/src/package1.0/package.tcl 2007-06-27 23:27:21 UTC > (rev 26535) > +++ trunk/base/src/package1.0/package.tcl 2007-06-27 23:45:18 UTC > (rev 26536) > @@ -33,6 +33,7 @@ > package provide mp_package 1.0 > > package require portrpm 1.0 > +package require portsrpm 1.0 > package require portpkg 1.0 > package require portmpkg 1.0 > package require portdmg 1.0 > Added: trunk/base/src/package1.0/portsrpm.tcl (0 => 26536) > --- trunk/base/src/package1.0/portsrpm.tcl > (rev 0) > +++ trunk/base/src/package1.0/portsrpm.tcl 2007-06-27 23:45:18 UTC > (rev 26536) > @@ -0,0 +1,234 @@ > +# et:ts=4 > +# portsrpm.tcl > +# $Id: portsrpm.tcl $ > +# > +# Copyright (c) 2002 - 2003 Apple Computer, Inc. > +# All rights reserved. > +# > +# Redistribution and use in source and binary forms, with or without > +# modification, are permitted provided that the following conditions > +# are met: > +# 1. Redistributions of source code must retain the above copyright > +# notice, this list of conditions and the following disclaimer. > +# 2. Redistributions in binary form must reproduce the above > copyright > +# notice, this list of conditions and the following disclaimer > in the > +# documentation and/or other materials provided with the > distribution. > +# 3. Neither the name of Apple Computer, Inc. nor the names of its > contributors > +# may be used to endorse or promote products derived from this > software > +# without specific prior written permission. > +# > +# THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND > CONTRIBUTORS "AS IS" > +# AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED > TO, THE > +# IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A > PARTICULAR PURPOSE > +# ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT OWNER OR > CONTRIBUTORS BE > +# LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR > +# CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT > OF > +# SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR > BUSINESS > +# INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, > WHETHER IN > +# CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR > OTHERWISE) > +# ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF > ADVISED OF THE > +# POSSIBILITY OF SUCH DAMAGE. > +# > + > +package provide portsrpm 1.0 > +package require portutil 1.0 > +package require portfetch 1.0 > + > +set org.macports.srpm [target_new org.macports.srpm srpm_main] > +target_runtype ${org.macports.srpm} always > +target_provides ${org.macports.srpm} srpm > +target_requires ${org.macports.srpm} checksum > + > +options package.destpath > + > +set_ui_prefix > + > +proc srpm_main {args} { > + global portname portversion portrevision UI_PREFIX > + > + ui_msg "$UI_PREFIX [format [msgcat::mc "Creating SRPM package > for %s-%s"] ${portname} ${portversion}]" > + > + return [srpm_pkg $portname $portversion $portrevision] > +} > + > +proc srpm_pkg {portname portversion portrevision} { > + global UI_PREFIX package.destpath portdbpath destpath workpath > distpath prefix portresourcepath categories maintainers description > long_description homepage epoch portpath distfiles fetch_urls > + global os.platform os.arch os.version > + > + set rpmdestpath "" > + if {![string equal ${package.destpath} ${workpath}] && ![string > equal ${package.destpath} ""]} { > + set pkgpath ${package.destpath} > + system "mkdir -p ${pkgpath}/BUILD" > + system "mkdir -p ${pkgpath}/RPMS" > + system "mkdir -p ${pkgpath}/SOURCES" > + system "mkdir -p ${pkgpath}/SPECS" > + system "mkdir -p ${pkgpath}/SRPMS" > + set rpmdestpath "--define '_topdir ${pkgpath}'" > + } > + > + foreach dir [list "${prefix}/src/macports/SRPMS" "${prefix}/src/ > apple/SRPMS" "/usr/src/apple/SRPMS" "/macports/rpms/SRPMS"] { > + foreach arch {"src" "nosrc"} { > + set rpmpath "$dir/${portname}-${portversion}-$ > {portrevision}.${arch}.rpm" > + if {[file readable $rpmpath] && ([file mtime ${rpmpath}] >= > [file mtime ${portpath}/Portfile])} { > + ui_debug "$rpmpath" > + ui_msg "$UI_PREFIX [format [msgcat::mc "SRPM > package for %s-%s is up-to-date"] ${portname} ${portversion}]" > + return 0 > + } > + } > + } > + > + set specpath ${workpath}/${portname}-port.spec > + # long_description, description, or homepage may not exist > + foreach variable {long_description description homepage > categories maintainers} { > + if {![info exists $variable]} { > + set pkg_$variable "" > + } else { > + set pkg_$variable [set $variable] > + } > + } > + set category [lindex [split $categories " "] 0] > + set license "Unknown" > + set maintainer $maintainers > + > + set dependencies {} > + # get deplist > + set deps [make_dependency_list $portname] > + set deps [lsort -unique $deps] > + foreach dep $deps { > + set name [lindex [split $dep /] 0] > + set vers [lindex [split $dep /] 1] > + # don't re-package ourself > + if {$name != $portname} { > + lappend dependencies "${name} >= ${vers}" > + } > + } > + > + # true = .src.rpm (with distfiles), false = .nosrc.rpm (without > distfiles) > + set src false > + > + #set sourcespath ${prefix}/src/macports/SOURCES > + set sourcespath "`rpm --eval %{_sourcedir}`" > + > + system "cp -p ${portpath}/Portfile ${sourcespath}/$portname- > Portfile" > + system "cd ${portpath} && zip -r -q ${sourcespath}/$portname- > files.zip files -x \\*.DS_Store -x files/.svn\\*" > + foreach dist $distfiles { > + system "cp -p ${distpath}/${dist} ${sourcespath}/${dist}" > + } > + > + write_port_spec ${specpath} $portname $portversion > $portrevision $pkg_description $pkg_long_description $pkg_homepage > $category $license $maintainer $distfiles $fetch_urls $dependencies > $epoch $src > + system "rpmbuild -bs -v --nodeps ${rpmdestpath} ${specpath}" > + > + return 0 > +} > + > +proc make_dependency_list {portname} { > + set result {} > + if {[catch {set res [mport_search "^$portname\$"]} error]} { > + global errorInfo > + ui_debug "$errorInfo" > + ui_error "port search failed: $error" > + return 1 > + } > + foreach {name array} $res { > + array set portinfo $array > + > + if {[info exists portinfo(depends_build)] || [info exists > portinfo(depends_lib)]} { > + # get the union of depends_build and depends_lib > + # xxx: only examines the portfile component of the > depspec > + set depends {} > + if {[info exists portinfo(depends_build)]} { eval > "lappend depends $portinfo(depends_build)" } > + if {[info exists portinfo(depends_lib)]} { eval > "lappend depends $portinfo(depends_lib)" } > + > + foreach depspec $depends { > + set dep [lindex [split $depspec :] end] > + > + # xxx: nasty hack > + if {$dep != "XFree86"} { > + eval "lappend result [make_dependency_list $dep]" > + } > + } > + } > + lappend result $portinfo(name)/$portinfo(version) > + unset portinfo > + } > + ui_debug "dependencies for ${portname}: $result" > + return $result > +} > + > +proc write_port_spec {specfile portname portversion portrevision > description long_description homepage category license maintainer > distfiles fetch_urls dependencies epoch src} { > + set specfd [open ${specfile} w+] > + set origportname ${portname} > + regsub -all -- "\-" $portversion "_" portversion > + regsub -all -- "\-" $portname "_" portname > + puts $specfd "\#Spec file generated by MacPorts > +%define distribution MacPorts > +%define vendor MacPorts > +%define packager ${maintainer} > + > +Summary: ${description} > +Name: ${portname} > +Version: ${portversion} > +Release: ${portrevision} > +Group: ${category} > +License: ${license} > +URL: ${homepage} > +BuildRoot: %{_tmppath}/%{name}-%{version}-root > +Epoch: ${epoch} > +Source0: ${portname}-Portfile > +Source1: ${portname}-files.zip" > + set first 2 > + set count $first > + puts $specfd "#distfiles" > + foreach file ${distfiles} { > + > + puts -nonewline $specfd "Source${count}: " > + if {![info exists $fetch_urls]} { > + foreach {url_var distfile} ${fetch_urls} { > + if {[string equal $distfile $file]} { > + global portfetch::$url_var > + set site [lindex [set $url_var] 0] > + set file [portfetch::assemble_url $site $distfile] > + break > + } > + } > + } > + puts $specfd $file > + if (!$src) { > + puts $specfd "NoSource: $count" > + } > + incr count > + } > + puts $specfd "" > + puts $specfd "AutoReqProv: no" > + if {[llength ${dependencies}] != 0} { > + foreach require ${dependencies} { > + puts $specfd "BuildRequires: [regsub -all -- "\-" $require "_"]" > + } > + } > + puts $specfd " > +%description > +${long_description} > + > +%prep > +%setup -c -a 1 -T > +cp -p %{SOURCE0} Portfile > +#prepare work area > +port fetch > +port checksum > +port extract > +port patch > + > +%build > +port configure > +port build > + > +%install > +rm -rf \$RPM_BUILD_ROOT > +mkdir -p \$RPM_BUILD_ROOT > +port destroot > +port rpm > + > +%clean > +port clean" > + close $specfd > +} > Modified: trunk/base/src/port1.0/portutil.tcl (26535 => 26536) > --- trunk/base/src/port1.0/portutil.tcl 2007-06-27 23:27:21 UTC (rev > 26535) > +++ trunk/base/src/port1.0/portutil.tcl 2007-06-27 23:45:18 UTC (rev > 26536) > @@ -1166,7 +1166,8 @@ > archive - > pkg - > mpkg - > - rpm - > + rpm - > + srpm - > dpkg - > activate - > "" { set deptypes "depends_lib depends_build depends_run" } > _______________________________________________ > macports-changes mailing list > macports-changes(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo/macports-changes

1 0

Re: MacPorts guide & Wiki
by Randall Wood 28 Jun '07

28 Jun '07

On Wednesday, June 27, 2007, at 09:58AM, "Daniel J. Luke" <dluke(a)geeklair.net> wrote: >On Jun 27, 2007, at 5:38 AM, Randall Wood wrote: >> 3) The guide never migrated from the opendarwin.org servers. We >> haven't had it on the web and there is an open ticket for the >> ability to write static documents in wordpress on macosforge.org >> that is still unaddressed after 9 months.[1] MacPorts controls the >> port distribution chain in a way that we don't control the >> macosforge.org site. > >If it's just a matter of getting it up somewhere, I (and I'm sure >others) have webspace where it could be hosted (at least temporarily). A number of use could host the guide and if there was a portfile for it we could use the portfile to ensure that all hosted copies of the guide were quickly and trivially updated no less. -- Randall Wood rhwood(a)mac.com "The ball is round. The game lasts ninety minutes. The rest is theory..."

3 5

MacPorts guide & Wiki
by Juan Manuel Palacios 28 Jun '07

28 Jun '07

Hey Maun Suang! Your recent work on the guide has caught my eye and made me very interested! We've been trying to revive such an important documentation effort for a while already with many false starts, so first off I want to thank you for taking a real lead in it! Landon and I have been talking about putting the guide back up on our site once again even if it's not fully up to date, and start improving it little by little, baby steps, 'cause every single gigantic effort till this day to provide the project with the greatest documentation ever in one fell swoop has failed. Therefore baby steps to the rescue, just as you're doing right now! One of my explicit goals with this mail is to encourage you to keep on working on the guide as your spare time permits you and to assure you that your time will not be wasted, at all! There are of course the questions of where exactly we'd put the generated guide (the html docs) and how we would go about automating it's regeneration, which is something I already ping'd Kevin Van Vechten on. Once I have some leads from him I'll get back to you and this list with details. One other topic is how we should integrate that source of information with the Wiki, and on this I hope to not tread too harshly on what's already been discussed many times before, of which I don't have much track at all to be honest (and I apologize to people involved for that!). In any case, Wiki docs being as dynamic as they are, I was mainly thinking we should use the Wiki solely for "How-To" type of documents, like how to setup a mail server with MacPorts installed software and edit it as new information and packages become available. On the other hand, existing wiki documentation on the basics of how to use MacPorts, how to become a member, how to properly submit tickets, Portfile writing guidelines and the like should be moved to the guide if not already there, officially and emphatically endorsed by the project (not that the wiki isn't endorsed, but the guide seems to me like more formal). Thoughts? On the contribution topic, there are those with commit bit already (who should feel free to dive in and and work on the official docs, I'm sure peer review will help stabilize things) and those who don't have +commit but still might want to contribute. I see many, many solutions to the latter, so many in fact that I fear this thread getting lost in endless discussion on how to channel it, as it's happened before. I'll start by proposing the following: I create a "Documentation" milestone up in the roadmap, where users can upload either patches and/or comments on the docs (in case they don't know how to create patches) and committers review and apply them as appropriate; those contributors without +commit and with a good record get promoted to project membership. On the wiki side of things, I'll fulfill one of my promises and coordinate with kvv an easier way of granting wiki write privileges to a selected subset of people whom we approve to write wiki documentation, so that "how-to" documents are also fluently created and maintained. Again, I'm really fearing loosing this thread to endless debate once again, so I'll go ahead and start with the outlined plan unless someone proves me that it is fundamentally flawed because of <insert your best possible argument here>. If it happens to fall short of ideal, we can always improve it as we move along, but I'm sure we would all appreciate at least *some* forward progress on the sorry state of our documentation over nothing at all. So, people (Maun Suang ;-), start your engines! -jmpp

4 7

Status of Jaguar support?
by Ryan Schmidt 28 Jun '07

28 Jun '07

Is MacPorts officially no longer supporting Jaguar? What happens if you try to install MacPorts on Jaguar? What happens if you manage to install MacPorts on Jaguar -- can you run it? I see changes were committed to the documentation indicating only 10.3 and later are supported. I see several ports including darwin 6 platform selectors that just output a message that the port doesn't work on that platform. If we are officially no longer supporting Jaguar, then MacPorts should decline to install on that OS, port should decline to run on that OS, and we should remove all darwin 6 platform selectors from all ports.

5 5

Updating the GMTL Port
by Doug McCorkle 27 Jun '07

27 Jun '07

Hello, I would like to update the GMTL Port with the attached portfile. Thanks. Doug

2 2

Re: MacPorts guide & Wiki
by Daniel J. Luke 27 Jun '07

27 Jun '07

On Jun 27, 2007, at 2:25 PM, Juan Manuel Palacios wrote: >> To make it complete you still need the css file, however, so I'll >> try looking that up for you if it's not already in svn. Thanks for >> all the help and human & machine time, Daniel, much appreciated! > > Can you try the trunk/doc/guide/resources/docbook.css file? I > think that's the one that was governing the guide feel and look, > but currently I don't have the necessary software installed to test > it (I can't regen the html files) yeah, that's it. I just built the html target which doesn't copy it over and use it like the xhtml target does. -- Daniel J. Luke +========================================================+ | *---------------- dluke(a)geeklair.net ----------------* | | *-------------- http://www.geeklair.net -------------* | +========================================================+ | Opinions expressed are mine and do not necessarily | | reflect the opinions of my employer. | +========================================================+

1 0

Re: [26461] users/pipping/merge.rb
by Ryan Schmidt 27 Jun '07

27 Jun '07

On Jun 24, 2007, at 08:57, source_changes(a)macosforge.org wrote: > Revision: 26461 > http://trac.macosforge.org/projects/macports/changeset/26461 > Author: pipping(a)macports.org > Date: 2007-06-24 06:57:23 -0700 (Sun, 24 Jun 2007) > > Log Message: > ----------- > initial upload of <merge.rb> > > merge.rb is designed to merge two or more trees of single-arch > destdirs > into a single destdir of universal binaries. Now, what it is this? You may recall I mentioned the "unify" script on the mailing list some time ago, which based on your description, does what your merge.rb script does. Why reinventing the wheel? http://lists.macosforge.org/pipermail/macports-dev/2007-March/ 000864.html http://lists.macosforge.org/pipermail/macports-dev/2007-April/ 001319.html

4 7

sudo port install glitz +universal
by Ryan Schmidt 27 Jun '07

27 Jun '07

I have plenty of ports installed with +universal, but glitz is complaining: $ sudo port install glitz +universal Error: Error executing universal: Default universal variant only works with ports based on configure Error: Unable to execute port: Error evaluating variants But glitz _is_ based on configure. It's a perfectly normal, simple port. Debug output shows it's actually complaining about the XFree86 dependency: $ sudo port -dv install glitz +universal Password: DEBUG: Found port in file:///Users/rschmidt/macports/dports/graphics/ glitz DEBUG: Changing to port directory: /Users/rschmidt/macports/dports/ graphics/glitz DEBUG: Requested variant darwin is not provided by port glitz. DEBUG: Requested variant i386 is not provided by port glitz. DEBUG: Requested variant macosx is not provided by port glitz. DEBUG: Executing variant universal provides universal DEBUG: Found port in file:///Users/rschmidt/macports/dports/x11/XFree86 DEBUG: Changing to port directory: /Users/rschmidt/macports/dports/ x11/XFree86 DEBUG: Requested variant i386 is not provided by port XFree86. DEBUG: Executing variant universal provides universal DEBUG: Default universal variant only works with ports based on configure [snip] But I'm not even using XFree86; I'm using Apple's X11 quite happily. I tried "sudo port -n install glitz +universal" to try to Not follow dependencies, but it makes no difference. How do I get around this and install glitz +universal?

2 5

Some questions about the new molden port
by Jochen Küpper 26 Jun '07

26 Jun '07

On 26.06.2007, at 20:21, source_changes(a)macosforge.org wrote: > Log Message molden: convert portfile from iso-8859-1 to utf-8 Are Portfiles per definition UTF-8? Is that documented somewhere? I cold not find anything by searching the MacPorts Wiki. If UTF-8 is required, is it ok to add a Local Variables section to the end of the files, so Emacs automatically uses the correct file coding? Like this: ## Local Variables: ## coding: utf-8 ## End: Moreover, I have agreed with the author of molden to include a banner at the end of the install process to ask the user kindly to register his use of molden. Therefore I have added the following code to the Portfile: post-install { ui_info "**************************************************" ui_info "In order to keep up support for Molden, proof that" ui_info "it is being used outside the CMBI is required." ui_info "Please register your copy of molden at:" ui_info "*** http://www.cmbi.ru.nl/molden/ form.html ***" ui_info "**************************************************" } However, this is not printed on my own system. What would be the correct way of doing this? Greetings, Jochen -- Einigkeit und Recht und Freiheit http://www.Jochen- Kuepper.de Liberté, Égalité, Fraternité GnuPG key: CC1B0B4D Sex, drugs and rock-n-roll

2 2