On Feb 7, 2008, at 21:23, Esteban Barahona wrote:
Asunto: "port: command not found" after installing
MacPorts-1.6.0-10.5-Leopard.dmg
I downloaded the latest package to install macports; but the "port
command" doesn't work.
I read the guide up to 2.4. MacPorts and the Shell (at http://
gui
Asunto: "port: command not found" after installing MacPorts-1.6.0-10.5-
Leopard.dmg
I downloaded the latest package to install macports; but the "port
command" doesn't work.
I read the guide up to 2.4. MacPorts and the Shell (at http://guide.macports.org
)
after disabling "invisible files"
On Feb 7, 2008, at 02:46, Christoph Ludwig wrote:
On Wed, Jan 02, 2008 at 08:08:12PM +0100, Christoph Ludwig wrote:
On Wed, Jan 02, 2008 at 12:50:20PM -0600, Ryan Schmidt wrote:
On Jan 2, 2008, at 02:18, Christoph Ludwig wrote:
I have a request: I'd be grateful if support for mutt's gpgme
On Feb 7, 2008, at 10:25, Lenore Horner wrote:
The maintainer has said he doesn't use it any more and therefore
disinterest in upgrading the port.
gnucash has no maintainer at this time.
___
macports-users mailing list
macports-users@lists.macos
Ryan,
On Feb 7, 2008 8:37 PM, Ryan Schmidt <[EMAIL PROTECTED]> wrote:
>
> On Feb 7, 2008, at 19:26, Michael Franz wrote:
>
> > I have installed lesstif but the development header files are
> > missing. Does macports have a version that includes the headers?
> > Where would I get Xm/Xm.h?
>
> Mac
Rainer,
On Feb 7, 2008 8:36 PM, Rainer Müller <[EMAIL PROTECTED]> wrote:
> Michael Franz wrote:
> > Hi,
>
> Hi,
>
> First of all, *-devel has nothing to do with headers or stuff needed for
> developers only. *-devel ports are newser versions of the port, mostly
> considered unstable.
>
I guess I
On Feb 7, 2008, at 19:26, Michael Franz wrote:
I have installed lesstif but the development header files are
missing. Does macports have a version that includes the headers?
Where would I get Xm/Xm.h?
MacPorts does not use -devel ports for this purpose. (MacPorts -devel
ports serve an
Michael Franz wrote:
Hi,
Hi,
First of all, *-devel has nothing to do with headers or stuff needed for
developers only. *-devel ports are newser versions of the port, mostly
considered unstable.
I have installed lesstif but the development header files are missing.
Does macports have a ve
Hi,
I have installed lesstif but the development header files are missing. Does
macports have a version that includes the headers? Where would I get
Xm/Xm.h?
Michael
___
macports-users mailing list
macports-users@lists.macosforge.org
http://lists.macos
On Feb 7, 2008, at 11:19 AM, [EMAIL PROTECTED] wrote:
Patching configure is going to be very fragile.
Daniel> On the other hand, if you patch the inputs to configure,
you
Daniel> then depend on having autoconf installed on the end user's
Daniel> machine.
Why would that be a problem
I'll take a look. This might come in handy later.
I post a question to the icedtea list and they fixed the configure script
for me.
On to my next issue!
On Feb 7, 2008 11:41 AM, Rainer Müller <[EMAIL PROTECTED]> wrote:
> Michael Franz wrote:
> > Since I cannot figure out how to get aclocal, auto
>> Patching configure is going to be very fragile.
Daniel> On the other hand, if you patch the inputs to configure, you
Daniel> then depend on having autoconf installed on the end user's
Daniel> machine.
Why would that be a problem? Can't the portfile just specify the
dependency
I have emacs @22.1_1+darwin_8 (active) on Tiger (up to date).
If I start ($~/emacs) emacs from my home directory and run C-h i I get the
message Can't find the Info directory node.
But, if I start ($/opt/local/bin/emacs-22.1) emacs from the macports
installation directoryC-h i it will load the *inf
James Berry wrote:
I guess a positive to the code is that it does for Leopard provide
enable at least minimal MacPorts usage if PATH isn't set, and also
gets MANPATH set, which unfortunately doesn't happen by default on
Leopard.
So users will keep it that way and install additional software fr
On Feb 7, 2008, at 9:28 AM, Anders F Björklund wrote:
Rainer Müller wrote:
Paths in /etc/manpaths.d and /etc/paths.d are always added at the
end of MANPATH and PATH. Therefore, installs by MacPorts will not
override the default Mac OS X installation. As it is not possible
to prepend ne
On Feb 7, 2008, at 9:08 AM, Triston Whetten wrote:
Take a gander at http://trac.macports.org/projects/macports/ticket/13472
.
Thank you. I had tried to search the bug reports before posting, but
I must have done something silly in my search.
Cheers,
-j
smime.p7s
Description: S/MIME c
Rainer Müller wrote:
Paths in /etc/manpaths.d and /etc/paths.d are always added at the
end of MANPATH and PATH. Therefore, installs by MacPorts will not
override the default Mac OS X installation. As it is not possible
to prepend new paths, this option is rather useless for us.
I think
On 2008-02-07, at 16:53, Jordan K. Hubbard wrote:
On Feb 7, 2008, at 2:45 AM, Jochem Huhmann wrote:
There's no way to take that further (in the file system) by
integrating even more useful fuzziness like recognizing "f" for
"ph", or ignoring accents or whatever. If you're dealing with
i
Michael Franz wrote:
Since I cannot figure out how to get aclocal, automake and autoconf to
run in the pre-configure step I have to patch configure.
What about:
use_automake yes
use_autoconf yes
http://guide.macports.org/#reference.phases.configure.automake-autoconf
Rainer
___
You need to open a specific port. I think it's 873.
Stef
Hello,
I have the same problem as described. I'm on Leopard.
I have "bash" output for "basename $SHELL" command. It seems correct.
MANPATH is correct if I try to get it through env command.
DISPLAY variable is DISPLAY=/tmp/launch-hpEjq8
I have it running on a PowerBook G4 with 10.4.11. I don't have much
installed but Gnucash and Gimp. I haven't been replying, because I
had to ask for help to get one or the other to install, but don't
remember what I actually had to do. Gnucash is out of date so there
is a bug you may run
Ryan Schmidt wrote:
On Feb 6, 2008, at 18:47, Jeffrey Goldberg wrote:
Ah. I don't know what the "right" way of doing things is, but after
poking around I added a file, /etc/manpaths.d/Macports the contents of
which are
/opt/local/share/man
which seemed to solve that problem for me.
Woul
On Feb 7, 2008, at 2:45 AM, Jochem Huhmann wrote:
There's no way to take that further (in the file system) by
integrating even more useful fuzziness like recognizing "f" for
"ph", or ignoring accents or whatever. If you're dealing with
international users a case insensitive file system may
Take a gander at http://trac.macports.org/projects/macports/ticket/
13472.
Triston.
On Feb 7, 2008, at 8:54 AM, Mike Procario wrote:
On 2/7/08, Jeffrey Goldberg <[EMAIL PROTECTED]> wrote: When I
get a chance later today, I'll submit a proper bug report, but
I wanted to know if anyone has
On 2/7/08, Jeffrey Goldberg <[EMAIL PROTECTED]> wrote:
>
> When I get a chance later today, I'll submit a proper bug report, but
> I wanted to know if anyone has gnucash from macports running.
>
> To briefly summarize, when I install guile and slib-guile and build
> gnucash with
>
> -guile16 +w
On Feb 6, 2008, at 10:33 PM, [EMAIL PROTECTED] wrote:
Michael> I need to change the way configure works for a port. Is
it
Michael> better to patch configure or change the underlying files
and
Michael> regenerate configure?
Patching configure is going to be very fragile. Your patch
When I get a chance later today, I'll submit a proper bug report, but
I wanted to know if anyone has gnucash from macports running.
To briefly summarize, when I install guile and slib-guile and build
gnucash with
-guile16 +without_docs
gnucash builds fine, but fails on start-up with a s
NTFS is case insensitive and case preserving by default, but can be
made case sensitive.
Take SFU (Services For Unix) that runs on win32 systems. It shows
some of the technical ability of windows (though I'm no fan of
Windows). It runs as a peer to the win32 subsystem (not on top of it
On 2/7/08, Jochem Huhmann <[EMAIL PROTECTED]> wrote:
>
>
> On 2008-02-06, at 21:13, Jordan K. Hubbard wrote:
>
> > That's probably never going to happen. When you're dealing with
> > grandma on the phone and she's saying "I can't open my file named
> > ``fluffy!''", the last thing you need is to g
On 2008-02-06, at 21:13, Jordan K. Hubbard wrote:
That's probably never going to happen. When you're dealing with
grandma on the phone and she's saying "I can't open my file named
``fluffy!''", the last thing you need is to go 10 rounds trying to
figure out whether she actually named it F
Heh, I tried running a case-sensitive file system for a while, and with
Leopard I took the opportunity to switch back. It's a hellish experience
if you expect things to "just work".
The problem is really that applications break spectacularly when they
run into such an issue, and the only way t
On Wed, Jan 02, 2008 at 08:08:12PM +0100, Christoph Ludwig wrote:
> On Wed, Jan 02, 2008 at 12:50:20PM -0600, Ryan Schmidt wrote:
> > On Jan 2, 2008, at 02:18, Christoph Ludwig wrote:
> > >I have a request: I'd be grateful if support for mutt's gpgme
> > >crypto backend
> > >was added to the port
On Feb 6, 2008, at 8:17 PM, Ryan Schmidt wrote:
On Feb 6, 2008, at 19:12, David Rowe wrote:
Ryan Schmidt wrote:
The libidl bug is a different and unrelated bug. libidl is
unmaintained so someone will have to volunteer to figure out
what's breaking, and how to fix it. Actually, Tod Morri
33 matches
Mail list logo
