PortAuthority 6.1 released

Code by Kevin has released PortAuthority 61, a GUI for the MacPorts Unix software management system for Mac OS X. PortAuthority provides a graphical user interface for the MacPorts software management system for Mac OS X. MacPorts is a powerful command-line tool for installing and updating a v

Re: tiff revbump?

On Apr 13, 2014, at 16:51, Ryan Schmidt wrote: > > On Apr 13, 2014, at 10:57, mk-macpo...@techno.ms wrote: > >> Yesterday I noticed - while installing a MacPorts from scratch - that after >> all the port tiff got rebuild by rev-upgrade. >> >> Looks like tiff would need a revbump right? >> >

Re: Is there a way to figure out which deps would have to be build from sources

On Apr 12, 2014, at 2:12 PM, Eric Gallager wrote: > > On Sat, Apr 12, 2014 at 4:55 PM, wrote: > Hi devs, > > I just wonder whether someone out there > has already written some script > which can determine for any given port A > whether non-binary

Re: [MacPorts] howto/PatchLocal modified

On Apr 13, 2014, at 19:48, MacPorts wrote: > Page "howto/PatchLocal" was changed by j...@opus1.com > Diff URL: > > Revision 7 > Comment: I tried "port patch xxx-devel" as recommended, and this tried to > fetch "xxx-devel"

Re: Questions re CI on Macports and KDE

On 14 Apr 2014, at 02:09 , Ryan Schmidt wrote: > These answers are in the OS X Mavericks software license agreement: Thanks so much for your citation. I have stolen them right away and replanted them on [1] >> - How can he get in contact with the MacPorts CI guys? > admin at macosforge dot or

Re: tiff revbump?

On 14 Apr 2014, at 02:07 , Brandon Allbery wrote: > rev-upgrade catches these silent errors and corrects them. I know that it does that. I’ve often run into traps like that in the past and it’s so much better now with rev-upgrade in place taken care of all of that. :-) _

Re: Questions re CI on Macports and KDE

On Apr 13, 2014, at 16:06, Ian Wadham wrote: > But first, Ben has some basic questions and he would like to get in touch > with the guys who run MacPorts' CI system to discuss possibilities. There > are potential benefits for both sides, it appears. I have told him what > MacPorts' CI does, tha

Re: Puzzling inconsistency regarding dep

Hi, > On 14 Apr 2014, at 01:52 , Ryan Schmidt wrote: > > By definition, a build dependency isn’t needed at runtime, so you wouldn’t > > distribute it, so you wouldn’t care about build dependencies’ > > distributability, would you? > > Hmmm, you’ve got your point. > When I was writing those lines

Re: tiff revbump?

On Sun, Apr 13, 2014 at 7:56 PM, wrote: > The only idea I had was that I started the whole MacPorts installation > from scratch and it ran perhaps for 4 hrs (with a 1h of short > interruptions) and somewhere in between I saw rev-upgrade rebuilding tiff… > So, I thought that some other dependency

Re: Puzzling inconsistency regarding dep

On 14 Apr 2014, at 01:52 , Ryan Schmidt wrote: > By definition, a build dependency isn’t needed at runtime, so you wouldn’t > distribute it, so you wouldn’t care about build dependencies’ > distributability, would you? Hmmm, you’ve got your point. When I was writing those lines I awaited this k

Re: tiff revbump?

Hi Ryan, On 14 Apr 2014, at 01:51 , Ryan Schmidt wrote: > If a binary on our packages server is mislinked (i.e. linked with a previous > version of a dependency’s library) such that rev-upgrade decides to rebuild > it, we should revbump to fix the binary package. OK. > However, I looked at one

Re: Puzzling inconsistency regarding dep

On Apr 13, 2014, at 14:24, mk-macpo...@techno.ms wrote: > On 13 Apr 2014, at 21:12 , Joshua Root wrote: >> What would this warning say, and where would it go? And have you read >> the help for port rdeps? > > Ah, sorry, now I see that there is indeed an option "--no-build" there. > > But still,

Re: tiff revbump?

On Apr 13, 2014, at 10:57, mk-macpo...@techno.ms wrote: > Yesterday I noticed - while installing a MacPorts from scratch - that after > all the port tiff got rebuild by rev-upgrade. > > Looks like tiff would need a revbump right? > > > How is the policy regarding such cases?? > > Shall

Re: Questions re CI on Macports and KDE

Hi Ian, I just want to add something as well as answer some of your questions (with what I found via Google). On 13 Apr 2014, at 23:06 , Ian Wadham wrote: > Ben is not sure what would be required to set up CI of KDE in an Apple > OS X envirionment. His immediate questions are to do with Apple

Questions re CI on Macports and KDE

Hello MacPorts Developers, As you may know, I am a developer of KDE Games working on Apple OS X Lion with an early-2011 Macbook Pro. I am here on a kind of diplomatic mission from KDE-land. But first a few words of background. KDE SC 4.13 is due for release on 16 April. Just over a month ago,

Re: Puzzling inconsistency regarding dep

On 13 Apr 2014, at 21:12 , Joshua Root wrote: > What would this warning say, and where would it go? And have you read > the help for port rdeps? Ah, sorry, now I see that there is indeed an option "--no-build" there. But still, one could make use of an option like “--with-build” for the rdepend

Re: License handling

On 2014-4-14 05:08 , mk-macpo...@techno.ms wrote: > Hi devs, > > I have found [1-6] discussing how licenses are being handled on MacPorts. > Browsing our Guide I couldn’t find any section containing license rules. > According to [7] we’ve got only port_binary_distributable.tcl [8] as some > sort

Re: Puzzling inconsistency regarding dep

On 2014-4-14 02:31 , mk-macpo...@techno.ms wrote: > On 13 Apr 2014, at 18:01 , Brandon Allbery wrote: >> Well, this is still highlighting an inconsistency. > Yes, right you are, otherwise I wouldn’t have stumbled over it. I don't think it's inconsistent, the information being expressed is just in

License handling

Hi devs, I have found [1-6] discussing how licenses are being handled on MacPorts. Browsing our Guide I couldn’t find any section containing license rules. According to [7] we’ve got only port_binary_distributable.tcl [8] as some sort of license documentation. Shouldn’t we have more that our Gui

Re: Puzzling inconsistency regarding dep

On 13 Apr 2014, at 19:08 , Jeremy Lavergne wrote: > Using verbose (port -v) might list out the types of dependencies. The only difference I can see here is that the -v version puts “port:” in front of the port names… What am I missing? — $ port deps gtk2 Full Name: gtk2 @2.24.23_0+x11 Extract De

Re: Puzzling inconsistency regarding dep

Using verbose (port -v) might list out the types of dependencies. On April 13, 2014 12:01:11 PM EDT, Brandon Allbery wrote: >On Sun, Apr 13, 2014 at 11:51 AM, wrote: > >> On 13 Apr 2014, at 17:46 , Brandon Allbery >wrote: >> > Looks like it's because it's a build dependency --- so, while the >g

Re: Puzzling inconsistency regarding dep

On 13 Apr 2014, at 18:01 , Brandon Allbery wrote: > Well, this is still highlighting an inconsistency. Yes, right you are, otherwise I wouldn’t have stumbled over it. > In this case, I think it's between the actual record of dependencies in the > package registry (produced by actually installing

Re: Puzzling inconsistency regarding dep

On Sun, Apr 13, 2014 at 11:51 AM, wrote: > On 13 Apr 2014, at 17:46 , Brandon Allbery wrote: > > Looks like it's because it's a build dependency --- so, while the gtk2 > port is what pulled it in, it is not needed at runtime. > Ahhh, I see. > Thanks for solving this mystery! :-) Well, this is

tiff revbump?

Yesterday I noticed - while installing a MacPorts from scratch - that after all the port tiff got rebuild by rev-upgrade. Looks like tiff would need a revbump right? How is the policy regarding such cases?? Shall one simply commit a revbump whenever one spots a port like that

Re: Puzzling inconsistency regarding dep

On 13 Apr 2014, at 17:46 , Brandon Allbery wrote: > Looks like it's because it's a build dependency --- so, while the gtk2 port > is what pulled it in, it is not needed at runtime. Ahhh, I see. Thanks for solving this mystery! :-) Greets, Marko ___ mac

Re: 2.3.0

Am 04.04.14 02:10, schrieb Ryan Schmidt: 1. I changed the way the environment variables are output, to be sorted and one per line: https://trac.macports.org/ticket/40703 This is easier to read. However for reasons I don’t understand, I don’t always see them in log output; sometimes I just se

Re: Puzzling inconsistency regarding dep

On Sun, Apr 13, 2014 at 10:39 AM, wrote: > But if I let port show me all kmymoney4-devel deps it gets listed: > — > $ port rdeps kmymoney4-devel > ... > kde4-runtime > kdelibs4 > soprano > libiodbc > gtk2 > gtk-doc > … > — > > So, the question is, why the

Puzzling inconsistency regarding dep

Hi, port gtk-doc puzzled me just now, since it doesn’t seem to have dependent ports. — $ port rdependents gtk-doc gtk-doc has no dependents. — But if I let port show me all kmymoney4-devel deps it gets listed: — $ port rdeps kmymoney4-devel ... kde4-runtime kdelibs4 soprano li

Re: [118847] trunk/dports/science/gnuradio

On Apr 12, 2014, at 12:03, michae...@macports.org wrote: > Revision > 118847 > Author > michae...@macports.org > Date > 2014-04-12 10:03:02 -0700 (Sat, 12 Apr 2014) > Log Message > > gnuradio: > + update devel to 76970d54 and next to 4d93231b, both 20140411; > + move to using the github PortGrou