October 2006 - macports-dev - lists.macosforge.org

Gnopernicus has 3 missing dependencies
by Mark Duling 10 Oct '06

10 Oct '06

Gnopernicus' 1.1.2 won't install without gconf, libgnome, and libgnomeui ports also installed. https://svn.macosforge.org/projects/macports/ticket/10829 I take it this is how Gnome bugs are to be reported now? Mark

1 0

Revised proposal for a new Wiki structure
by Mark Duling 09 Oct '06

09 Oct '06

Here is a revised proposal. There are other ways to organize it so comments or other proposals are welcome. Mark -------------------------------------- *** Section 1 - Getting Started with MacPorts *** I) Home Page II) Installing MacPorts (This section is complete and up on the Wiki now) 1) Install Xcode Tools 2) Install X11 3) Set the shell environment 4) Install the MacPorts Binary 5) Run 'port selfupdate' to get the latest portfiles III) Using MacPorts (Joe's Getting Started section) IV) Gnome V) FAQ *** Section 2 - Getting Support for MacPorts *** I) Trac 1) Search for bugs 2) Filing bugs II) Mailing lists *** Section 3 - MacPorts Development *** I) MacPorts Internals 1) Build Phases II) Making Portfiles (or Portfile examples if that is too challenging) III) MacPorts Guide (enhanced legacy guide - reference material) IV) New Committer's Guide V) Developer FAQ ---------------------------------------- >Where would you place pages like the GNOME page? > >On 8 Oct 2006, at 22:12, Mark Duling wrote: > >> I added a page to the Wiki to more or less comprehensively cover >> MacPorts >> installation: Installiing MacPorts, X11, setting the shell. Right >> now it >> is OS X 10.4 only. Comments are welcome. >> >> http://trac.macosforge.org/projects/macports/wiki/InstallingMacPorts >> >> I'd like to delete the ManuallySettingShell at the top-level since it >> isn't needed anymore. I also propose the structure as shown below >> for the >> Wiki. I think the current structure needs improvement. >>

1 0

New ports tickets
by Cédric Luthi 07 Oct '06

07 Oct '06

Hello, I was wondering who should be assigned when one submits a new port in the trac. I found nowhere information about that, maybe it would be good to explain that in the wiki. I assigned my new port (https://svn.macosforge.org/projects/macports/ ticket/10838) to yeled(a)macports.org as I did with my preceding port when we had no choice who to assign the ticket to. But are some people responsible for specific categories ? Is one people responsible for new ports ? Cédric

1 0

Naming convention for pre-release versions
by Michel Salim 05 Oct '06

05 Oct '06

I was trying to the lame Portfile earlier, and had trouble persuading the port manager that 3.97 is newer than 3.97b2 (in the end I uninstalled 3.97b2 and ran the install from the same directory as the updated Portfile). Is there a convention for naming such pre-release versions? I'm thinking of the Fedora Extras-esque '3.97-0.beta2', where the alpha/beta release gets encoded in the revision field, and always preceded by a '0'. The final version can then be revision 1, and everyone's happy. Regards, -- Michel Salim http://www.cs.indiana.edu/~msalim http://the-dubois-papers.blogspot.com/

2 1

Need a referee - BUG or RFE?
by Mark Duling 04 Oct '06

04 Oct '06

Can I get a vote on whether the snippet below from bug 10226 represents a feature request or a bug? Being the bug Nazi is a thankless job. :) Mark http://trac.macosforge.org/projects/macports/ticket/10226 -------------- (2) It is a BUG, not an enhancement request. port is not "most programs", it is a database management system. Any action that changes the database should be encapsulated in a transaction, and it should be rolled back on anything but normal completion of the task. If this facility can't be added to port, then at least trap all aborts and all error terminations (at least the deactivation of random prerequisities can occur without an abort), and report "DANGER! DANGER! DANGER! MacPorts is possibly corrupt! Be prepared for complete loss of functionality in random programs!" I don't know enough about port to be able to make concrete suggestions, but surely there's enough information available for port to make more specific warnings, and perhaps do some error recovery, even in the case of the user pushing the panic button. ----------------------

4 4

Announcement: special new maintainer addresses
by James Berry 04 Oct '06

04 Oct '06

As described here <http://trac.macports.org/projects/macports/wiki/ SpecialMaintainerAddresses>, we have created two new email addresses to replace the special 'darwinports(a)opendarwin.org' that was previously in use. Please let me know if you have any questions about this. Thanks to kvv for getting these addresses set up. James

2 1

Announcement: Call for new port committers
by James Berry 04 Oct '06

04 Oct '06

MacPorts is soliciting new committers. If you have written or maintained ports, and are interested in commit status to keep those ports up to date, please send email with the subject "Request for commit access" to <macports-mgr(a)lists.macosforge.org>. In doing so, please also tell us: - What ports you have written or worked on (output from "port echo maintainer:your-email-here" is always helpful). Or if you have filed bugs for ports that have not yet been committed, please reference the bug #'s. We recognize that our existing committer base cannot always respond appropriately to the change load required for ports, and are asking you, our users, to step in and respond. In return, we want to be more accepting of new committers. Note that we see policing of committers as a community responsibility. If you feel that the the committer for a port is not responding properly or wisely, please email the committer, and if you get no response, apply to adopt the port. James

1 0

Re: Delivery Status Notification (Failure)
by James Berry 04 Oct '06

04 Oct '06

On Oct 3, 2006, at 7:43 AM, Michael Stevens wrote: > On Tue, Oct 03, 2006 at 10:38:14AM -0400, Daniel J. Luke wrote: >> We should probably update all of "darwinports(a)darwinports.org" >> instances to something else. > > Maybe update them all to macports-dev? Our plan is to switch to two new addresses: nomaintainer(a)macports.org (meaning that there is no maintainer) and openmaintainer(a)macports.org (meaning that any committer is free to update the port: this must only be used in conjunction with one or more other "responsible" committers for the port). We've just been waiting for these aliases to be created... ;( James

2 1

added ljclive patch to trac
by Michael Stevens 02 Oct '06

02 Oct '06

Hi. I've added an update to the net/clive portfile to trac: https://svn.macosforge.org/projects/macports/ticket/10818 This updates clive to the current release. Michael

1 0

assigned-to address for bugs in the base component
by Vincent Lefevre 02 Oct '06

02 Oct '06

On Trac, is it normal that bugs in the base component are assigned to darwinports-bugs(a)opendarwin.org? -- Vincent Lefèvre <vincent(a)vinc17.org> - Web: <http://www.vinc17.org/> 100% accessible validated (X)HTML - Blog: <http://www.vinc17.org/blog/> Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)

1 0