Vincent Lefevre wrote:
While different python versions are incompatible, different perl
versions should be compatible (there are very few backward
incompatibilities, but modules based on them should be seen as buggy).
So, I'd say that perl5.10 should completely replace perl5.8, i.e. it
should
On Sat, Jan 12, 2008 at 10:17:15PM -0500, Luis O'Shea wrote:
Could someone commit the new port for asymptote? See ticket #13249
(http://trac.macosforge.org/projects/macports/ticket/13249).
Thanks,
Luis
Hi,
I just committed it [1] with one minor change. I added a post-activate hook with
Hi ...
the Changes of the Portfile for gtkglext needs to get committed. #13624
http://trac.macports.org/projects/macports/ticket/13624
The Maintainer seems to doesn't respond.
After this is done, #13517 (http://trac.macports.org/projects/
macports/ticket/13517)
can be closed (dealing with
Hi
Could someone commit the update of qucs to 0.0.13? See Ticket: #13826
http://trac.macports.org/projects/macports/ticket/13826
Thanks,
Rolf
--
Security is an illusion - Datasecurity
twice
Rolf Würdemann- private: [EMAIL PROTECTED] -
On Jan 13, 2008, at 9:30 AM, Simon Ruderich wrote:
On Sat, Jan 12, 2008 at 10:17:15PM -0500, Luis O'Shea wrote:
Could someone commit the new port for asymptote? See ticket #13249
(http://trac.macosforge.org/projects/macports/ticket/13249).
Thanks,
Luis
Hi,
I just committed it [1] with one
On Jan 13, 2008, at 2:29 PM, Luis O'Shea wrote:
On Jan 13, 2008, at 9:30 AM, Simon Ruderich wrote:
On Sat, Jan 12, 2008 at 10:17:15PM -0500, Luis O'Shea wrote:
Could someone commit the new port for asymptote? See ticket #13249
(http://trac.macosforge.org/projects/macports/ticket/13249).
Anfang der weitergeleiteten E-Mail:
Von: Rolf Würdemann [EMAIL PROTECTED]
Datum: 13. Januar 2008 20:03:18 MEZ
An: Luis O'Shea [EMAIL PROTECTED]
Betreff: Re: New port needs commit
Am 13.01.2008 um 19:59 schrieb Luis O'Shea:
On Jan 13, 2008, at 9:30 AM, Simon Ruderich wrote:
On Sat, Jan
Hi Blair,
Executable startupitems are the preferred type. Daemondo can track pids
automatically and reliably restart an application if it quits. See the
guide on this:
http://guide.macports.org/#reference.startupitems
Given how startupitem executables work, I don't see an advantage to
Hi Mark,
I was seeing the following:
1) One dhcpd would start.
2) Every 10 seconds thereafter, another dhcpd would be started, but it
couldn't bind to the port since the first one was running.
It appears that the startupitem infrastructure wasn't keeping track of
dhcpd running and
After the commit, I uninstalled asymptote, removed the reference
to my local port hierarchy from sources.conf, and did a selfupdate.
Why did you do that? What did the entry that you removed look
like, and what lead you to the conclusion that you needed to remove
it in the first place?
Hi Mark,
The guild says this:
startupitem.executable. Specifies the name of the daemon to be run
in the background. It may have multiple arguments, but they must be
appropriate for a call to exec; arbitrary shell code may not be used.
Should the actual daemon remain in the foreground so
Mark,
It works fine if I use this:
startupitem.create yes
startupitem.namedhcpd
startupitem.executable ${prefix}/sbin/dhcpd -f
startupitem.netchange yes
How's that?
Regards,
Blair
On Jan 13, 2008, at 12:36 PM, Blair Zajac wrote:
Hi Mark,
The guild says this:
Blair,
I see. That's fine then. I just wanted to be sure there was a reason for
making it a script startupitem and there is. I'm cc'ing James (master of
all things startupitem) just in case he knows why the executable
startupitem type wasn't adequate in this case. It seems like it should
have
Mark,
It works fine if I use this:
startupitem.create yes
startupitem.name dhcpd
startupitem.executable ${prefix}/sbin/dhcpd -f
startupitem.netchange yes
How's that?
The startupitem executable is preferred if it works automatically I think;
but if it doesn't for some reason at
Hi Mark,
So it looks like the bit magic that got this to work is the -f
command, which basically tells dhcpd not to daemonize, which would be
a good thing in our case, as the process of daemonizing would look to
daemondo or launchd as if dhcpd were exiting, which would cause the
Luis O'Shea wrote:
After the commit, I uninstalled asymptote, removed the reference to my
local port hierarchy from sources.conf, and did a selfupdate. However
port seemed to not find the new asymptote port:
% port info asymptote
Error: Port asymptote not found
The PortIndex is regenerated
Rainer Müller wrote:
Luis O'Shea wrote:
After the commit, I uninstalled asymptote, removed the reference to my
local port hierarchy from sources.conf, and did a selfupdate. However
port seemed to not find the new asymptote port:
% port info asymptote
Error: Port asymptote not found
The
On Jan 13, 2008, at 4:02 PM, Luis O'Shea wrote:
After the commit, I uninstalled asymptote, removed the reference
to my local port hierarchy from sources.conf, and did a selfupdate.
Why did you do that? What did the entry that you removed look
like, and what lead you to the conclusion
Le 11 janv. 08 à 21:48, Ryan Schmidt a écrit :
On Jan 11, 2008, at 10:25, [EMAIL PROTECTED] wrote:
Revision: 32697
http://trac.macosforge.org/projects/macports/changeset/
32697
Author: [EMAIL PROTECTED]
Date: 2008-01-11 08:25:00 -0800 (Fri, 11 Jan 2008)
Log Message:
Luis O'Shea wrote:
Two questions:
- What is the best description of the ports referenced by
file:///...? I called it my local port hierarchy, but I now think
this might be confusing. (It might mean my *copy* of
rsync://rsync.macports)
I would call it an overlay. A term coming from my
On 12/01/2008, at 10:24 AM, Ryan Schmidt wrote:
I was led to believe that an epoch should never be decreased, ever,
once it has been added to a portfile, even if the port's version is
increased. I understood that the epoch takes precedence over the
version.
I'm pretty sure that that's
Sorry, meant to send this to macports-users ;-) But some testing from
this audience wouldn't hurt either :-P
-jmpp
On Jan 14, 2008, at 1:17 AM, Juan Manuel Palacios wrote:
As some of you may have seen, I've been improving the postflight
script in the release_1_6 branch with the
As some of you may have seen, I've been improving the postflight
script in the release_1_6 branch with the feedback I've received so
far, plus some other relevant fixes/improvements. The final product is
what will be in the 1.6.1 pkg installer, which I plan to upload to our
website to
23 matches
Mail list logo
