#Macports building time full#
#Macports building time software#
#Macports building time code#

Note that in order to interact with Trac for anything other than read only operations, you need Source browser and the project timeline (where ticket activityĬan also be viewed). Seamless read-only integration with our git repository through its We use the popular Trac web-based tool for our bug tracking and Wiki needs, thus buying ourselves

#Macports building time full#

Project with full write access to our git repository and Wiki pages, either to work on MacPorts itself or as a ports This is also where you should turn to if you are a developer and/or a contributor interested in joning The MacPorts Request or if you wish to discuss anything you might feel is of private nature (like the interaction between MacPorts and “PortMgr”), in case you have any administrative List is where you should send mail to in case you need to get in touch with the The MacPorts Project's management team (A.K.A. The private and read-only “ macports-mgr ” mailing Of choice (English), and reducing the number and size of attachments in any way possible (e.g, by using paste bins suchĪs GitHub Gist and passing along the paste URL rather than full error messages). That are common to most open forums when posting of particular relevance is sticking to plain text messages, our language Members are expected to abide by the very simple Netiquette guidelines Note that due to spam control policies you must subscribe to our non read-only lists in order to post to any of them. Read-only, low volume list for project related major announcements. Read-only, moderate volume list of ticket activity on our Trac bug tracker Read-only, moderate volume list with build notifications from our Buildbot

#Macports building time code#

Read-only, low to moderate volume list of changes to our git repository on GitHubįor both “base” code and Portfiles, among others. Where project members and contributors discuss the MacPorts “base” system itself and futureĭevelopment plans, and related “Portfile” writing best practices. General discussion of MacPorts installation and usage. The MacPorts Project hosts a number of specialized mailing lists you can freely subscribe to:

#Macports building time software#

any third party software that may exist in places such as /usr/local and/or /sw.Or PowerPC), and the version of Xcode installed - the “ sw_vers” and “ uname -a” commands are of platform details such as operating system version (e.g.

output generated by the “ port” command's -v (verbose) or -d.

Finally, if you still haven't found the answer to your problem, send e-mail to the appropriate mailing list.

Second, check the archives of the appropriate mailing list you intend to post to (below) to see if your question.

First and foremost, check the MacPorts Documentation, man pages, FAQ and problems hotlist.

The following simple steps comprise our recommended procedure to obtain support: Much information about your host platform as you can gather will help us help you in turn to look into the problem.

If you're looking for help to troubleshoot a particular failure installing or using MacPorts, providing us with as On who you need to contact and the type of support and/or feedback you're looking for: There are a number of ways in which you can get in contact with people involved with The MacPorts Project, depending