On Jun 19, 2008, at 9:41 PM, Boyd Waters wrote:
> So here's a fundamental question: why can't we set port parameters in
> the macports.conf?
>
> Then if the option is set in the Portfile, it overrides what is in the
> macports.conf. And if the user specifies it on the command line, that
> override
On Jun 19, 2008, at 4:22 PM, [EMAIL PROTECTED] wrote:
> Revision: 37697
> http://trac.macosforge.org/projects/macports/changeset/37697
> Author: [EMAIL PROTECTED]
> Date: 2008-06-19 14:22:46 -0700 (Thu, 19 Jun 2008)
> Log Message:
> ---
> science/glue: initial 1.17 release
On Jun 19, 2008, at 5:57 PM, Rainer Müller wrote:
> Boyd Waters wrote:
>> So if I set configure.compiler in macports.conf, it gets picked up
>> unless overridden in the Port file?
>
> There is no option yet in macports.conf, that's what I am proposing
> here.
>
> Currently you can only use i
Boyd Waters wrote:
> So if I set configure.compiler in macports.conf, it gets picked up
> unless overridden in the Port file?
There is no option yet in macports.conf, that's what I am proposing here.
Currently you can only use it from command line, but this will override
configure.compiler fro
On Jun 18, 2008, at 10:11 PM, Ryan Schmidt wrote:
> If there's an option you want to have set globally, it should be in
> the macports.conf
So if I set configure.compiler in macports.conf, it gets picked up
unless overridden in the Port file?
Is that documented anywhere?
_
This is fixed. Thanks for reporting it.
-Bill
On Jun 19, 2008, at 9:48 AM, Rainer Müller wrote:
Rainer Müller wrote:
I just tried to attach a file to ticket #15679 [1], but Trac only
gave me a red message "Internal error". I tried several times, but
it does not work. I don't know if the
Rainer Müller wrote:
> I just tried to attach a file to ticket #15679 [1], but Trac only gave
> me a red message "Internal error". I tried several times, but it does
> not work. I don't know if there is more information I could provide.
The title tag contains at least an error message:
[Errno 13
Hi,
I just tried to attach a file to ticket #15679 [1], but Trac only gave
me a red message "Internal error". I tried several times, but it does
not work. I don't know if there is more information I could provide.
I am reporting this via mail because I am not sure if Trac is working
normally.
Dear community member,
in cooperation with the software engineering research group at Free
University of Berlin (Freie Universität Berlin), we are currently
conducting an empirical survey on time consumption of participants in
Open Source/Free Software projects.
In this survey we want to find out
> Quick question: in macports svn, is doc obsolete and only doc-new in
> use anylonger?
I would say yes. As you can see in the repository browser [1] doc
>>hasn't
gotten any commits in 9 months, which is when doc-new was created.
>>>
>>> so should we maybe get rid of it?
>>
>>+1,
Quick question: in macports svn, is doc obsolete and only doc-new in
use anylonger?
>>> I would say yes. As you can see in the repository browser [1] doc
>hasn't
>>> gotten any commits in 9 months, which is when doc-new was created.
>>
>> so should we maybe get rid of it?
>
>+1, removes c
11 matches
Mail list logo
