Re: [120217] trunk/dports/graphics/tiff/Portfile

Hi, > I've been trying to solve this problem, but tiff's build system is > horrible and is not making it easy for me. Here's the ticket under > which I'm working on this: > > https://trac.macports.org/ticket/43642 We could add a way for Portfiles to request being run in trace mode automatically

MacPorts 2.3.0-rc2 now available for testing

Source code and pkg/dmgs for MacPorts 2.3.0-rc2 are now available [1]. Testing of either of these install methods is helpful. Be prepared to encounter bugs. As always, having a recent backup would be wise. Please report any bugs that you find [2] (after first searching Trac [3], of course!) If no

Re: [120217] trunk/dports/graphics/tiff/Portfile

On 20 May 2014, at 01:10 , Ryan Schmidt wrote: > I undid the revbump, to save users from needlessly reinstalling the port if > they haven't already. Oh, thanks, Ryan! ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosfor

Re: [120217] trunk/dports/graphics/tiff/Portfile

On May 19, 2014, at 18:05, mk-macpo...@techno.ms wrote: > Hi Ryan, > > On 20 May 2014, at 01:01 , Ryan Schmidt wrote: >> Yeah, it's good if commit messages can explain why a change is being made. > Yes, I know. Was a little to fast there, i admit. > >> Just saying that you're revbumping a port

Re: [120217] trunk/dports/graphics/tiff/Portfile

Hi Ryan, On 20 May 2014, at 01:01 , Ryan Schmidt wrote: > Yeah, it's good if commit messages can explain why a change is being made. Yes, I know. Was a little to fast there, i admit. > Just saying that you're revbumping a port isn't informative; I'd like to be > able to see e.g. which library h

Re: MacPorts port of LaTeXML

On May 19, 2014, at 17:35, Bruce Miller wrote: > On 05/06/2014 12:32 PM, Bruce Miller wrote: >> On 05/06/2014 12:08 PM, Brandon Allbery wrote: >>> On Tue, May 6, 2014 at 11:50 AM, Bruce Miller wrote: >>> >>>I have a draft of an updated Portfile, > [...] >>>how might I go about suggesting t

Re: [120217] trunk/dports/graphics/tiff/Portfile

On 20 May 2014, at 00:30 , Ryan Schmidt wrote: > On May 19, 2014, at 13:50, m...@macports.org wrote: >> tiff: revbump needed > Why did it need a revbump? I see now that my rebump didn’t actually help, since even with the freshly rev-bumped tiff I once again get a rebuild of tiff on another VM:

Re: [120217] trunk/dports/graphics/tiff/Portfile

On May 19, 2014, at 17:54, Marko wrote: > On 20 May 2014, at 00:30 , Ryan Schmidt wrote: >> On May 19, 2014, at 13:50, m...@macports.org wrote: >>> tiff: revbump needed >> Why did it need a revbump? > > I had reoccurring tiff-rebuilds here and couldn’t figure out why it always > got rebuilt on s

Re: [MacPorts] InstallingMacPorts modified

Oops, did not see this before updating in https://trac.macports.org/wiki/InstallingMacPorts?action=diff&version=74 ... anyways, the directions on how to install it with MacPorts are under there, too, but that is just one way to do it. While it might be better to install it with MacPorts, the user s

Re: MacPorts port of LaTeXML

On 05/06/2014 12:32 PM, Bruce Miller wrote: On 05/06/2014 12:08 PM, Brandon Allbery wrote: On Tue, May 6, 2014 at 11:50 AM, Bruce Miller mailto:bruce.mil...@nist.gov>> wrote: I have a draft of an updated Portfile, [...] how might I go about suggesting this port for inclusion in th

Re: [120217] trunk/dports/graphics/tiff/Portfile

On May 19, 2014, at 13:50, m...@macports.org wrote: > Revision > 120217 > Author > m...@macports.org > Date > 2014-05-19 11:50:03 -0700 (Mon, 19 May 2014) > Log Message > > tiff: revbump needed Why did it need a revbump? ___ macports-dev mailing li

Re: [MacPorts] #43731: ola: use "github.tarball_from releases"

It seems to be up again if you want to take a look now. On May 19, 2014, at 12:47, Simon Newton wrote: > Trac is down, so I can't see the diff. > > Simon ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/ma

Re: [MacPorts] InstallingMacPorts modified

On May 19, 2014, at 17:00, Eric Gallager wrote: > On Fri, May 16, 2014 at 10:28 PM, Ryan Schmidt wrote: > >> On May 11, 2014, at 20:47, MacPorts wrote: >> >> > Page "InstallingMacPorts" was changed by eg...@gwmail.gwu.edu >> > Diff URL: >> >

Re: [MacPorts] InstallingMacPorts modified

I was under the impression that the recommendation to install X11 was just a recommendation, and not actually a requirement... The section does not actually say that installing X11 is a requirement to use MacPorts, it just says that it is highly recommended for many MacPorts apps. Although I suppos

Re: Identifying more situations for interactivity

On 2014-5-19 22:32 , Clemens Lang wrote: > Hi, > >> Please suggest more such cases. > > I think you forgot the use case I suggested in the meeting last week: > > $> port uninstall foobar > "foobar" isn't indisputable. Which of the following ports do you want to > uninstall? > (1) foobar @0.0.

Re: "ticket" port command?!

On May 13, 2014, at 12:53 AM, Aljaž Srebrnič wrote: > On 13/mag/2014, at 06:10, Ryan Schmidt wrote: > >> >> On May 11, 2014, at 13:49, mk-macpo...@techno.ms wrote: >> >> >> I've been using a shell function to do this for years. > > Is it in contrib/? I’d like to take a look at it! This may

Re: [MacPorts] #42872: cmake PortGroup: don't add -I${prefix}/include to CXXFLAGS

On Apr 10, 2014, at 1:46 PM, MacPorts wrote: > #42872: cmake PortGroup: don't add -I${prefix}/include to CXXFLAGS > --+ > Reporter: mojca@… | Owner: macports-tickets@… > Type: defect | Status: new > Priority: Normal |

Re: Abandoning ports

Hi Brian, g5pw took over maintainership of the_silver_searcher in r120205. I have updated the other ports in r120212, r120214 and r120215. Thanks for letting us know and for contributing! Cheers! Frank On May 19, 2014, at 9:15 AM, Brian Hartvigsen wrote: > Just a notice that I will not b

Abandoning ports

Just a notice that I will not be maintaining the following ports in the future: libchloride libsodium py-parsedatetime the_silver_searcher -- Brian ___ macports-dev mailing list macports-dev@lists.macosforge.org https://lists.macosforge.org/mailman/list

Re: small doubt regarding gcc_select ...

Well, given the fact that the select ports influences mainly user's system behaviour, not macports itself, I intentionally posted to the user list, as users might want to express preferences. But of cause we can discuss this elsewhere and I will comment on the ticket that was created. Here th

Re: Identifying more situations for interactivity

Hi, > Please suggest more such cases. I think you forgot the use case I suggested in the meeting last week: $> port uninstall foobar "foobar" isn't indisputable. Which of the following ports do you want to uninstall? (1) foobar @0.0.1 +xzy (2) foobar @0.0.2 +xzy (3) foobar @0.0.3 Type a

Re: Identifying more situations for interactivity

On 2014-05-17 13:35, Shashwat Pandey wrote: > I am working on the Interactive Port Command project for GSoC 2014. > http://trac.macports.org/wiki/SummerOfCode#interactive > > The link above also has the list of all the use cases that i know of. I > need help of the list to identify more such cases