On Mon, Mar 24, 2014 at 11:31 PM, Clemens Lang wrote:
> Hi,
>
>> It would probably make sense to discuss and collect different ideas
>> somewhere (it could be Trac, but it's probably suboptimal at this
>> early stage of brainstorming where lots and lots of ideas could be
>> discussed, prioritized,
Hi,
> It would probably make sense to discuss and collect different ideas
> somewhere (it could be Trac, but it's probably suboptimal at this
> early stage of brainstorming where lots and lots of ideas could be
> discussed, prioritized, written down, ...).
I think we can keep discussing things on
This changes the library's install name. You need to revbump all ports.
Based on this being a tiny version update, I highly suspect upstream doesn't
know how to properly version their library. You should communicate this error
upstream and help them fix their library.
--Jeremy
On Mar 23, 201
On Mon, 24 Mar 2014 12:25:08 +0100, Peter Danecek wrote:
> I need to add some dependencies for one python port and this regards ONLY
> Python 2.6. The content of the package would not change. Do I need to bump
> the revision in this case?
>
> I would be inclined not to do so. The packages is unc
Hi all,
I need to add some dependencies for one python port and this regards ONLY
Python 2.6. The content of the package would not change. Do I need to bump the
revision in this case?
I would be inclined not to do so. The packages is unchanged and the changes
might affect only few (if any) py
On 2014-3-24 06:18 , Jeremy Huddleston Sequoia wrote:
> I'm considering adjusting compiler preferences in base trunk for Xcode >= 3.2
> as follows:
> 1) Add macports-clang-3.4 before macports-clang-3.3
> 2) Prefer macports-clang-* over other port-provided compilers
>
> So in general, we prefe
