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

Committer help requested
by David Evans 21 Mar '08

21 Mar '08

This is to solicit the help of some kind committer in reviewing the following two tickets: Upgrade gconf-editor to 2.22.0 (including registration of schemas with gconf) http://trac.macosforge.org/projects/macports/ticket/14742 Upgrade glade3 to 3.4.3 http://trac.macosforge.org/projects/macports/ticket/14622 Thanks Dave

1 0

new port search format
by Ryan Schmidt 21 Mar '08

21 Mar '08

I must say I find the new "port search" output format that's in trunk very hard to read. Before, we had roughly a table, and I could scan down the left column to read the port names. Now the description is in roughly the same place -- albeit indented by a couple spaces but it still interferes with my ability to scan the left column, which is no longer a column.

5 8

Ticket #14679
by Ross A. Beyer 21 Mar '08

21 Mar '08

dev, I'm new to submitting Trac tickets, and I "assigned" Ticket #14679 ( http://trac.macports.org/projects/macports/ticket/14679 ) to macports-tickets(a)lists.macosforge.org. However, in reading the documentation again, I see I should have "assigned" this ticket to the maintainer, minskim(a)bawi.org. Could you change that for me, so the maintainer can be properly contacted? Thanks. I informally e-mailed the maintainer a week before I submitted the ticket without a response, so they may not respond anyway. Thanks. Ross

2 1

Fwd: Guidance needed for fixing gnome
by Randall Wood 21 Mar '08

21 Mar '08

Should have sent to the mailing list... ---------- Forwarded message ---------- From: Randall Wood <randall.h.wood(a)alexandriasoftware.com> Date: Fri, Mar 21, 2008 at 4:03 AM Subject: Re: Guidance needed for fixing gnome To: Thomas Reifferscheid <reiffert(a)macports.org> On Thu, Mar 20, 2008 at 9:48 PM, Thomas Reifferscheid <reiffert(a)macports.org> wrote: > Hi, > > please help me to improve the gnome situation and validate Ticket 14729 [1] > to be correct. > > How should we proceed here? I think that the best (long term) way to succeed would be to create a gnome portgroup that provides port with some generic mechanism to discover the schema files that need installation and do it auto-magically. > Kind regards > Thomas > > [1] http://trac.macosforge.org/projects/macports/ticket/14729 > _______________________________________________ > macports-dev mailing list > macports-dev(a)lists.macosforge.org > http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev > -- 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

PortIndex2MySQL run failure on Thursday 2008-03-20 at 19:33:30
by macports-mgr＠lists.macosforge.org 21 Mar '08

21 Mar '08

Testing fail emails: 3

1 0

Guidance needed for fixing gnome
by Thomas Reifferscheid 21 Mar '08

21 Mar '08

Hi, please help me to improve the gnome situation and validate Ticket 14729 [1] to be correct. How should we proceed here? Kind regards Thomas [1] http://trac.macosforge.org/projects/macports/ticket/14729

1 0

PortIndex2MySQL run failure on Thursday 2008-03-20 at 17:33:11
by macports-mgr＠lists.macosforge.org 21 Mar '08

21 Mar '08

Testing fail emails: 3

1 0

Re: Splitting the guide
by markd＠macports.org 20 Mar '08

20 Mar '08

>> But as we are talking about the guide, I might also bring up another >> issue with the current presentation. I find it difficult to link to >> specific headlines. Could the headlines made clickable with a link >> target on themself? Or maybe some marker item on mouse-move like trac >> does? At the moment I always look into the source to find out how the >> anchor was named which is a little bit annoying. Consider this as a >> nice-to-have issue ;-) >> >> I already looked into the generation scripts for this, but it seems to >> use a xslt stylesheet provided completely by docbook, so I don't know if >> I would have to file my request there... >> >> Rainer > >Hi Rainer, > >I just tried this using DocBook but it didn't work for me. So I used a >simple >sed replacement to get this working. I created two examples: >http://ruderich.com/macports/guide-link.html >http://ruderich.com/macports/guide-title.html >The first one wraps the sections (h1-h9) in links so you can click on >them to >see the anchor. The second one adds a title attribute which should >display the >anchor when you mouse over it for some time. > >Please tell me which you like more and I will add it to the documentation >Makefile to add it to the guide. I don't understand. The TOC entries are all linkable, and the TOC entries correspond to the titles. What is it that is missing? Mark

3 3

Re: [34977] trunk/base
by Rainer Müller 20 Mar '08

20 Mar '08

eridius(a)macports.org wrote: > Revision > 34977 <http://trac.macosforge.org/projects/macports/changeset/34977> > Author > eridius(a)macports.org > Date > 2008-03-13 07:13:51 -0700 (Thu, 13 Mar 2008) > > > Log Message > > Add new --recursive option to port uninstall to uninstall dependents (#14637) I'm not quite happy with the name --recursive, because it does not imply in which direction we recurse. I would rather propose something like --with-dependents or --follow-dependents. Although this is longer, but much more clear. We were also talking about 'recursive dependencies' before, especially for 'port deps'. But in that case it was meant following dependencies, not dependents. So --recursive might really lead to confusion here. In order to provide a consistent interface, we should define two options for this. One for following dependencies and one for following dependents. (And even one for doing both?) Currently, we also have the global -R und -n flags which are only used by upgrade and -u which is used by uninstall and upgrade. In my opinion these should not be global because they are only used by one or two targets. Therefore these should use the same naming convention. Rainer

1 0

Re: [35110] trunk/dports/gnome/gnucash
by Ryan Schmidt 19 Mar '08

19 Mar '08

On Mar 17, 2008, at 12:47, reiffert(a)macports.org wrote: > Revision: 35110 > http://trac.macosforge.org/projects/macports/changeset/35110 > Author: reiffert(a)macports.org > Date: 2008-03-17 10:47:47 -0700 (Mon, 17 Mar 2008) > > Log Message: > ----------- > gnucash 2.2.4, fixing: > #14297 (Update gnucash) > #13316 (binreloc error) > #13472 (Fails to build on leopard) > #13852 (Fails to compile) [snip] > -default_variants +guile16 > +default_variants +guile16 +without-docs > -variant without_docs { > +variant without_docs description {Does not build gnucash-docs} { > depends_lib-delete port:gnucash-docs > } In the default variants, hyphen is not a valid character in variant names, and the variant is in fact named without_docs (with an underscore, not a hyphen). However, if you're going to make it the default to build without documentation, then the variant should be changed to be called "docs" (or "with_docs" if you insist on that nonstandard naming convention). Default variants are buggy during upgrades and should be avoided.

4 3