On Jun 11, 2008, at 01:15, Martin Krischik wrote:
>> I would say, if I had a vote (who does?), that whatever people are
>> willing
>> to use wins. It may not be elegant or state of the art, but the
>> best is the
>> enemy of the good, and good is usually good enough.
>
> I like to point out on
Zitat von "Jordan K. Hubbard" <[EMAIL PROTECTED]>:
> Well, to be fair, I thought I was trying to address that by suggesting
> that there should be a "top level doc project" - individual projects
> could point up to it just as easily as it could point down to them,
> but it would be a clear "docs p
On Jun 10, 2008, at 23:28, Tabitha McNerney wrote:
> I have been working on a script (written in Ruby) that takes the
> output of the port command-line program (as suggested by Rainer
> recently), and parses the output looking for either port
> dependencies or file dependencies (note: up un
Hi,
> I would say, if I had a vote (who does?), that whatever people are willing
> to use wins. It may not be elegant or state of the art, but the best is the
> enemy of the good, and good is usually good enough.
I like to point out one more aspect: *If* we are going for a new Wiki
we might as
>>> For a long time, I thought that when people were saying port, in this
>>> discussion, I thought the were referring to a port or a tcp/ip
>>> address.
>>> like localhost:80
>>
>> Clarity is one of the reasons that in the past I frequently used
>> the term
>> "MacPorts port" (to distinguish it fr
Hello all --
I have been working on a script (written in Ruby) that takes the output of
the port command-line program (as suggested by Rainer recently), and parses
the output looking for either port dependencies or file dependencies (note:
up until yesterday, file dependences were referred to ambi
On Jun 10, 2008, at 11:43, [EMAIL PROTECTED] wrote:
>> For a long time, I thought that when people were saying port, in this
>> discussion, I thought the were referring to a port or a tcp/ip
>> address.
>> like localhost:80
>
> Clarity is one of the reasons that in the past I frequently used
Ryan Schmidt wrote:
> The developer apparently received a cease and desist order in
> February 2008 and had to remove the files.
>
> http://www.hymn-project.org/forums/viewtopic.php?t=1314
>
> We don't seem to have the files on our mirror either.
>
> http://distfiles.macports.org/JHymn/
>
> The f
> On Jun 8, 2008, at 18:09, Joe Schnide wrote:
>
> >
> > The Intel iMac was built as a clone of the MacBookPro so
> > they should be pretty close to identical.
I was recently having difficulties building some ports on my MacBook
Pro, but no problems building the same programs on my Mac Pro. (The
On Jun 8, 2008, at 18:09, Joe Schnide wrote:
> At 6:04 AM -0500 6/8/08, Ryan Schmidt wrote:
>
>> On Jun 8, 2008, at 05:46, Joe Schnide wrote:
>>
>>> I had no problem installing deluge on a MacBookPro but am having
>>> a problem on
>>> an Intel iMac.
>>
>> What is the difference between the MacB
On Jun 10, 2008, at 15:59, Mack Johnson wrote:
> This port is no longer?
> ---> Attempting to fetch JHymn_0_9_2_source.zip from http://
> www.hymn-project.org/download/
> ---> Attempting to fetch JHymn_0_9_2_source.zip from http://
> svn.macports.org/repository/macports/distfiles/JHymn
> --->
This port is no longer?
---> Attempting to fetch JHymn_0_9_2_source.zip from
http://www.hymn-project.org/download/
---> Attempting to fetch JHymn_0_9_2_source.zip from
http://svn.macports.org/repository/macports/distfiles/JHymn
---> Attempting to fetch JHymn_0_9_2_source.zip from
http://svn.m
On Jun 10, 2008, at 9:27 AM, Lorin Rivers wrote:
Leaving aside the issue of what the best platform for sharing the
info might be. If nobody knows it's there, the kick-assingest wiki
server the world has or will ever see is not going to address my
suggestion in the slightest.
Well, to be
On Tue, Jun 10, 2008 at 12:00 PM, <
[EMAIL PROTECTED]> wrote:
Message: 11
Date: Tue, 10 Jun 2008 11:27:30 -0500
From: "Lorin Rivers" <[EMAIL PROTECTED]>
Subject: Re: New Howto
To: "Jordan K. Hubbard" <[EMAIL PROTECTED]>
Cc: MacPorts Users
Message-ID:
<[EMAIL PROTECTED]>
Content-Type: text
Jochen Küpper wrote:
> On 10.06.2008, at 16:26, Vincent BOUDON wrote:
>> I am really sorry to bother you again with this, but I have another
>> problem with molden on Mac OS X and I must admit that the way to
>> report this via trac.macports.org seems quite obscure to me ...
Our guide should s
On 10.06.2008, at 16:26, Vincent BOUDON wrote:
Thanks a lot, it worked fine.
I am really sorry to bother you again with this, but I have another
problem with molden on Mac OS X and I must admit that the way to
report this via trac.macports.org seems quite obscure to me ...
please report i
>For a long time, I thought that when people were saying port, in this
>discussion, I thought the were referring to a port or a tcp/ip address.
>like localhost:80
Clarity is one of the reasons that in the past I frequently used the term
"MacPorts port" (to distinguish it from FreeBSD and other po
Leaving aside the issue of what the best platform for sharing the info might
be. If nobody knows it's there, the kick-assingest wiki server the world has
or will ever see is not going to address my suggestion in the slightest.
My point was that it's quite a challenge finding the current how-to's ev
18 matches
Mail list logo
