Hi,
The output of the portindex commands depends on whether the character
set is UTF-8 or, e.g., ISO-8859-1, due to non-ASCII characters in a
description: the number after the port name seems to contain the
number of characters instead of the number of bytes. For instance,
I get:
On 2007-02-09 11:39:20 -0600, Ryan Schmidt wrote:
I assume that's due to the stupid setting available in emacs or vi or
whatever editor it is that actually encourages that behavior. The one
where they've said We want to indent to 4-space tabs. However, the
editor is configured to print 8
On 2007-02-12 23:21:45 -0600, Ryan Schmidt wrote:
On Feb 10, 2007, at 20:58, Vincent Lefevre wrote:
A mix of tabs and spaces is bad since it won't look right in diffs,
for instance.
What do you mean, won't look right in diffs?
Bad indentation, making the diff less readable.
What do you
On 2007-02-13 13:25:23 -0400, Juan Manuel Palacios wrote:
http://trac.macosforge.org/projects/macports/ticket/5275
As I said in my comment to this, I don't see much added value to a
portindex(1) man page, users shouldn't see themselves in the need of
indexing manually. And those who
On 2007-02-24 10:50:32 -0500, Daniel J. Luke wrote:
On Feb 24, 2007, at 7:54 AM, Vincent Lefevre wrote:
It is version 1.77. The version provided by the p5-math-bigint port
is 1.73 only. Is there a reason to keep such a port that is not
up-to-date and that will never be used because perl first
On 2007-02-25 11:12:48 -0500, Salvatore Domenick Desiano wrote:
Peering into the minds of Apple's documentation writers (I know, my
eyes will be burned), there may be a reason for this. -O turns on
optimization. The default is -O0 (no optimization), and there are
libraries that actually fail
On 2007-02-25 04:54:29 +0100, Elias Pipping wrote:
assuming you already have the port, updated. compare the output of
/opt/local/bin/gfile /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/
libncurses.5.4.dylib
and
/usr/bin/file /Developer/SDKs/MacOSX10.4u.sdk/usr/lib/libncurses.
On 2007-02-27 22:42:42 -0600, Ryan Schmidt wrote:
Well my disk is full, and I wouldn't have a clue how to use the
debugging info even if it were there, so I don't want it. So how do
we make the presence or absence of -g configurable globally per user?
Note that even if there isn't a global
For those who are in non-UTF-8 locales and use non-English locales
(with messages containing non-ASCII characters, such as accented
characters) and wonder if something gets wrong with these messages:
On my machine, all these messages suddenly appeared with undecoded
UTF-8 sequences, and I took me
On 2007-03-05 19:27:05 -0600, Ryan Schmidt wrote:
For example, if you want to change the indentation of the file, do
only that, then commit it, with a log message that says you're
changing the whitespace.
Some changes will also change the indentation as a consequence
(well, perhaps more
The following problem occurs with both the old version and 1.4 rc2:
prunille:~ sudo port -v uninstall m4 @1.4.8b_1
Error: port uninstall failed: Registry error: m4 1.4.8b_1 not registered as
installed.
prunille:~ sudo port -v upgrade m4
--- Activating m4 1.4.8b_1+with_default_names
Error:
On 2007-03-15 15:52:51 -0400, Kevin Ballard wrote:
The full spec for that installation is @1.4.8b_1+with_default_names.
Try using that in the uninstall.
Hmm... yes. It would be nive to accept @1.4.8b_1 too when there's no
ambiguity.
--
Vincent Lefèvre [EMAIL PROTECTED] - Web:
On 2007-03-17 13:00:50 -0700, [EMAIL PROTECTED] wrote:
Revision: 22884
http://trac.macosforge.org/projects/macports/changeset/22884
Author: [EMAIL PROTECTED]
Date: 2007-03-17 13:00:49 -0700 (Sat, 17 Mar 2007)
Log Message:
---
* cleanup
Modified Paths:
On 2007-03-20 03:46:42 -0400, Juan Manuel Palacios wrote:
On Mar 19, 2007, at 10:29 PM, Yves de Champlain wrote:
However, configure will always fail looking for malloc.h, so
wouldn't it be a good idea to have macports install a dummy
malloc.h ?
I personally don't think this is a good
$ sudo port -v upgrade lftp
Error: Variant ssl conflicts with tls
Error: Unable to upgrade port: 1
$ port installed lftp
The following ports are currently installed:
lftp @3.5.6_0+tls (active)
Even though ssl is the default variant, I don't think this is a correct
behavior for upgrade. I think
On 2007-03-28 13:05:23 +0200, Elias Pipping wrote:
On Mar 28, 2007, at 3:35 AM, Paul Guyot wrote:
It would be great if this could be tested more and released as soon as
possible:
- it would allow maintainers to work on universal variants
- it would allow us to simplify many portfiles by
On 2007-03-30 09:10:35 -0400, Daniel J. Luke wrote:
The macports change to always add -I and -L options isn't in a release
version (yet). We should probably think about it some more and do lots of
testing to make sure that it won't break many (any?) ports.
That's a reason why I think that
On 2007-03-31 03:34:50 -0500, Ryan Schmidt wrote:
With CFLAGS, LDFLAGS and friends, we have to be careful not to
overwrite but merely to append, in case some things are already
defined in those variables. For example, CFLAGS by default includes
-O2; if we overwrite CFLAGS we've just
On 2007-04-05 12:26:10 -0700, James Berry wrote:
The MacPorts project is pleased to announce the release of MacPorts v1.4.0.
Change log is at
http://trac.macosforge.org/projects/macports/browser/tags/release_1_4_0/base/ChangeLog.
Downloads are available at
On 2007-04-05 16:49:38 -0400, Daniel J. Luke wrote:
The problem IIRC has to do with mismatched headers and library.
Yes, probably because the Makefile is incorrect.
So you'll want to do
locate readline.h
and see if there's a stray one (in /usr/local/include, probably) that's
On 2007-04-06 09:31:56 -0400, Daniel J. Luke wrote:
On Apr 5, 2007, at 8:12 PM, Vincent Lefevre wrote:
On 2007-04-05 16:49:38 -0400, Daniel J. Luke wrote:
The problem IIRC has to do with mismatched headers and library.
Yes, probably because the Makefile is incorrect.
It is? Do you
On 2007-04-06 16:37:09 +0200, Vincent Lefevre wrote:
On 2007-04-06 09:31:56 -0400, Daniel J. Luke wrote:
On Apr 5, 2007, at 8:12 PM, Vincent Lefevre wrote:
On 2007-04-05 16:49:38 -0400, Daniel J. Luke wrote:
The problem IIRC has to do with mismatched headers and library.
Yes
On 2007-04-06 10:55:20 -0400, Daniel J. Luke wrote:
On Apr 6, 2007, at 10:37 AM, Vincent Lefevre wrote:
For some reason, CURL_CONFIG seems to be
set to /usr/bin/curl-config, though which curl-config outputs
/opt/local/bin/curl-config (that's a bug since it can lead to
inconsistent paths
On 2007-04-08 13:14:42 +0900, Paul Guyot wrote:
We cannot simply autoconf for readline for the following reasons:
(a) readline comes with two incompatible APIs.
(b) Apple's gcc reads /usr/local/include before /usr/include
This is the case under Linux, but I thought it wasn't under Mac OS X
On 2007-05-10 15:55:53 -0700, James Berry wrote:
On May 10, 2007, at 7:44 AM, Vincent Lefevre wrote:
It seems that selfupdate got broken:
prunille:~ sudo port -d selfupdate
DEBUG: Rebuilding the MacPorts base system if needed.
Synchronizing from file:///Users/vinc17/wd/macosx/dports
DEBUG
On 2007-05-10 17:41:57 -0500, Ryan Schmidt wrote:
On May 10, 2007, at 09:44, Vincent Lefevre wrote:
[...]
file:///Users/vinc17/wd/macosx/dports
file:///Users/vinc17/software/dports
rsync://rsync.macports.org/dpupdate/dports
But I use this for port installation only.
According to the change
On 2007-05-15 15:20:59 -0400, Kevin Ballard wrote:
Here's a possible solution - in $prefix/etc/ports/sources.conf, we could
have a [nosync] directive after a source to tell dportsync not to sync it.
Would that work for you?
It would be a good idea (in addition to the permission test).
--
On 2007-05-15 15:25:29 -0400, Kevin Ballard wrote:
BTW, I've already fixed this particular issue in trunk. Port will
now run svn as the user who owns the WC.
This doesn't work here:
Synchronizing from file:///Users/vinc17/wd/macosx/dports
Password:
It shouldn't ask any password (I have a
On 2007-05-18 22:14:05 +0200, N_Ox wrote:
I've yet another time forgot to reply to all~~
Well, this mail is not for nothing:
i'm pleased to tell you i've fixed this problem by making a soelim(1)
system call.
Great!
By the way, I'll add an 'examples' variant before commiting it — well,
I want to upgrade to python24 @2.4.4_1, but I get the following error:
prunille:~ sudo port -v -d upgrade python24
DEBUG: Found port in file:///Users/vinc17/software/dports/lang/python24
DEBUG: Found port in
On 2007-05-24 16:50:28 +1000, Boey Maun Suang wrote:
I'm having problems that I haven't seen before while trying to log onto
Trac. My attempts to do so over https just resulted in repeated requests
for my username and password, while doing so over http resulted in:
Login to trac failed!
prunille:~ sudo port -v -d uninstall docbook-xml-412
DEBUG: scrollkeeper depends on this port
DEBUG: scrollkeeper depends on this port
--- Unable to uninstall docbook-xml-412 4.1.2_0, the following ports depend
on it:
---scrollkeeper
---scrollkeeper
DEBUG: Please uninstall the ports that
On 2007-06-04 21:49:31 -0500, Ryan Schmidt wrote:
On Jun 4, 2007, at 21:14, Vincent Lefevre wrote:
prunille:~ port info scrollkeeper
Warning: Found 2 port scrollkeeper definitions, displaying first one.
I don't have that message when I port info scrollkeeper. Maybe you
have a local copy
On 2007-06-14 03:29:28 -0500, Ryan Schmidt wrote:
$ port livecheck maintainer:ryandesign
Error: Unable to execute port:
/opt/local/var/db/dports/build/_Users_rschmidt_macports_dports_graphics_ImageMagick/work/.darwinports.ImageMagick.state
is not writable - check permission on port
On 2007-08-20 03:36:38 -0500, Ryan Schmidt wrote:
We have the -t switch which we can turn on separately to activate
trace mode, which is helpful for discovering undeclared
dependencies. Is there a way that we could somehow see just the
mtree violations, without all the other verbose/debug
On 2007-08-22 10:13:18 -0400, Daniel J. Luke wrote:
On Aug 22, 2007, at 5:34 AM, Randall Wood wrote:
I understand that some directories under the proposed scheme may be large,
such as /p/p5, /p/py, /g/gn but it seems that this would not be any real
change from the current situation for the
On 2007-08-21 16:33:11 -0500, Ryan Schmidt wrote:
[...]
ld: Undefined symbols:
_rl_completion_matches
_rl_filename_completion_function
_rl_username_completion_function
/usr/bin/libtool: internal link edit command failed
make[2]: *** [Pextlib.dylib] Error 1
make[1]: *** [all] Error 1
make:
On 2007-08-22 18:11:55 +0200, Rainer Müller wrote:
Vincent Lefevre wrote:
'port dir portname' only lists the first directory (when a port is
present in several sources).
That's good, otherwise we wouldn't be able to do something like
cd $(port dir foo)
Yes, but one may want the one
I can no longer connect to https://svn.macosforge.org/.
Any information?
--
Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/
100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/
Work: CR INRIA - computer arithmetic / Arenaire project (LIP, ENS-Lyon)
On 2007-08-28 01:50:30 -0500, Ryan Schmidt wrote:
It turns out that if you just install the port normally, with
neither debug nor verbose output, mtree violations are already
easily visible. So no change to base is necessary.
The problem is that when one uses debug/verbose output, one gets so
On 2007-08-27 23:39:04 -0400, Juan Manuel Palacios wrote:
If I'm reading you correctly, you're proposing a Portfile only be accepted
as clean if it specifically states it doesn't violate the mtree? If so,
such functionality would require us going through every single one of our
Portfiles
MacPorts stores patchfiles in /opt/local/var/macports/distfiles/${name}
e.g. /opt/local/var/macports/distfiles/mpfr contains here:
-rw-r--r-- 1 root admin 787634 2007-07-24 16:10:58 mpfr-2.2.1.tar.bz2
-rw-r--r-- 1 root admin 872947 2007-08-29 15:38:57 mpfr-2.3.0.tar.bz2
-rw-r--r-- 1 root admin
On 2007-09-01 07:28:25 -0700, [EMAIL PROTECTED] wrote:
* Changed doc directory to ${name}-${version}.
I don't know if there has been a discussion about this, but is there
any reason to include the version, given the fact that two different
versions cannot be activated at the same time?
I find
On 2007-09-03 15:57:47 +0200, N_Ox wrote:
Recent autotools-based package doc directories default to
${name}-${version} (see libogg and libvorbis).
But why did they do such a change? Note that this is a setting that
comes from these particular packages, not from the autotools:
On 2007-09-03 16:39:35 +0200, Vincent Lefevre wrote:
Upstream patches are versioned: they are in different subdirectories.
But MacPorts doesn't care, unless I've missed something to have the
subdirectory taken into account.
Also, I tried specifying the directory after patchfiles, but port
does
On 2007-09-03 12:22:17 -0500, Ryan Schmidt wrote:
What portname suffix would you propose instead of -devel? -devel seems
ok to me -- it indicates that this will install the version currently being
developed by the developers, as opposed to the version that is stable and
has already been
On 2007-09-03 12:18:29 -0500, Ryan Schmidt wrote:
I also don't know if patchfiles/distfiles can be renamed after
download. In the absence of that feature, I recommend:
dist_subdir ${name}/${version}
(Instead of the default dist_subdir ${name})
Thanks, this solves the problem.
--
Vincent
I've noticed the following error:
$ svn log -r2 https://svn.macosforge.org/repository/macports
svn: Bogus date
--
Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/
100% accessible validated (X)HTML - Blog: http://www.vinc17.org/blog/
Work: CR INRIA - computer arithmetic / Arenaire
On 2007-09-04 00:38:15 +0200, Rainer Müller wrote:
GPLv2 is not necessarily incompatible with GPLv3.
It is.
GPL lets the original author choose how new versions apply to the
software. See paragraph 9 of the GPLv2 [1].
--snip--
| Each version is given a distinguishing version number. If
On 2007-09-11 01:26:28 -0700, [EMAIL PROTECTED] wrote:
--- trunk/dports/devel/ossp-cfg/Portfile 2007-09-11 08:16:38 UTC (rev
28901)
+++ trunk/dports/devel/ossp-cfg/Portfile 2007-09-11 08:26:27 UTC (rev
28902)
@@ -3,16 +3,21 @@
PortSystem 1.0
name ossp-cfg
On 2007-10-01 10:59:48 +1000, Boey Maun Suang wrote:
I can confirm that I get the same problem trying to build port:gcc41. I
haven't the time to read the upstream mailing list just now (thanks for the
link), but, assuming that this is considered a bug in Texinfo that will be
fixed, I'd
On 2007-10-30 12:43:52 +0100, Anders F Björklund wrote:
Weissmann Markus:
Yes, but I meant this to be a per-Portfile choice so a maintainer can mark
his/her port as being able to build in parallel. Doing this with the
sledgehammer for all ports that use 'make' might be a bit too much. ;)
On 2007-10-31 12:26:44 +0100, Markus Weissmann wrote:
On 31.10.2007, at 05:13, Vincent Lefevre wrote:
I disagree. Port maintainers should test their port to see if they
work with make -j.
Well, you cannot reliably test this. If you're lucky it might work
one time and fail the other.
So
On 2007-10-31 15:04:45 +0100, Markus Weissmann wrote:
On 31.10.2007, at 12:36, Vincent Lefevre wrote:
On 2007-10-31 12:26:44 +0100, Markus Weissmann wrote:
On 31.10.2007, at 05:13, Vincent Lefevre wrote:
I disagree. Port maintainers should test their port to see if they
work with make -j
On 2007-10-31 15:57:56 +0100, Markus Weissmann wrote:
So the discussion has narrowed to:
1.) disabled by default on an per-installation option:
Can be toggled system-wide (with default off); ports have to actively
deny a parallel build attempt;
2.) disabled by default on a per-port option
On 2007-11-18 02:13:04 -0400, Juan Manuel Palacios wrote:
I still have to find where that header is being set, since the
relevant field on the mailing list administration page doesn't have
any value (i.e. Mailman itself doesn't seem to be setting the
Reply-To we currently have on those
On 2007-11-19 19:00:45 -0400, Juan Manuel Palacios wrote:
What difference does it make to impose a Reply-To header at
the post-commit hook level or at the mailing list level? The overall
effect is the same.
Well, this was a general rule. If someone (who is not the post-commit
hook) sends
On 2007-12-07 00:17:04 -0400, Juan Manuel Palacios wrote:
My list of outstanding TODOs for the 1.6 release is almost empty after
finishing what I committed in r31774, directly to the release branch: a
rethought and rewritten postflight script to add PATH and MANPATH
settings as
On 2007-12-07 13:38:26 -0400, Juan Manuel Palacios wrote:
Adding our setting to MANPATH *only-if-it-already-exists* *and* if
we're not already in there was agreed here to be the lesser evil for
the time being, so that's what we're doing. If MANPATH does not exist at
all (different
On 2007-12-20 10:00:24 +0100, Anders F Björklund wrote:
http://trac.macports.org/projects/macports/ticket/13641
Perl 5.10.0 has now been released, so there are now two
stable port versions available: perl5.8 and perl5.10
Is there a need for two different ports?
--
Vincent Lefèvre [EMAIL
On 2007-12-20 12:52:48 -0500, Mark Gardner wrote:
There are some incompatible changes (see
http://search.cpan.org/~rgarcia/perl-5.10.0-RC2/pod/perl5100delta.pod#Incompatible_Changes),
so some might want to stick with 5.8.
I'd say that very few modules or scripts should be affected (if any),
On 2007-12-20 11:52:21 -0700, Boyd Waters wrote:
On Dec 20, 2007, at 2:09 AM, Vincent Lefevre wrote:
Is there a need for two different ports?
Since you can't specify a version when you install a port, or use a
port in a dependency, then I've been told to just go ahead and make
a separate
On 2007-12-21 10:34:00 -0500, robert delius royar wrote:
I compiled perl 5.10.0 with the same configuration that macports 5.8.8
used. [I have the perl5.8 port set as the primary perl interpretor and
have created links in /usr/local/[bin|lib|share] to make it so that
other software finds
On 2008-01-11 10:09:21 +0100, Anders F Björklund wrote:
Not sure if that is a great example. For now, _only_ perl5.8 provides
the ${prefix}/bin/perl program and perl5.10 doesn't provide it. Should
it follow the lead of python24/python25, where _none_ of the ports
supplies
On 2008-02-04 07:52:44 -0600, Ryan Schmidt wrote:
On Feb 4, 2008, at 06:51, js wrote:
What's happen after -devel port get officially released?
are they removed from svn?
Some maintainers do that. I think most just leave the -devel ports
around.
I think that both choices are a bad idea,
On 2008-02-04 11:27:24 -0600, Ryan Schmidt wrote:
Regarding the suggestion to rename all *-devel ports to *-latest, in
light of the above change, the name latest would indeed seem to be
clearer. It would also remove any potential confusion with the RPM -
devel packages, which IMHO would
On 2008-02-05 13:57:30 +0100, Thomas de Grivel wrote:
Then we would have to warn new users about -latest not being so stable
because intuitively I would like the latest version to be installed
but what retains me the the previous one is that it just works. For
the sake of stability I would
On 2008-02-07 15:21:41 +0100, Thomas de Grivel wrote:
2008/2/7, Ryan Schmidt [EMAIL PROTECTED]:
It was proposed that -devel ports should be updated to the latest
stable version, if the latest stable version is newer than the latest
development version. If we act on this proposal, then -latest
On 2008-02-07 09:47:45 -0500, Daniel J. Luke wrote:
On Feb 7, 2008, at 9:03 AM, Emmanuel Hainry wrote:
Seeing that there are 5 different postgresql port (7,
80, 81, 82, 83) makes me quite puzzled, which one is considered
stable?
Each postgres version in macports has an on-disk format that
On 2008-02-07 22:08:57 +0900, js wrote:
I agree with you,
but I think that the situation that devel-ver stable-ver is very
rare. I've never seen it. (By newer, you means the version number is
greater, right?)
It happens for tin almost each time a new stable version is released
(because it is
On 2008-02-07 23:00:14 +0900, js wrote:
If the developer call it as stable and the other's development,
Let' follow it.
Anyone who like to use newer can easily choose -devel one.
However this may be confusing for the end user, as depending on the
developers, unstable doesn't always mean the
The unison port has recently been upgraded from 2.13 to 2.27. The
problem is that the protocol has changed between these versions,
and unison 2.13 can't talk to unison 2.27:
http://trac.macosforge.org/projects/macports/ticket/14172
The only solution that can work in every case (because users
On 2008-02-17 08:36:37 -0500, Kevin Ballard wrote:
No, the solution here is to not do anything. Anybody using 2.13 needs to
upgrade if they want to work with 2.27. We are not in the business of
providing old port versions, and we *should not* be.
So, what about these old db, qt and automake
On 2008-02-17 09:15:47 -0500, Kevin Ballard wrote:
Right now we're providing the official, released, stable version. That's
what we should provide.
I agree that it should be provided. What I was requesting is that
2.13 be provided as well (but 2.27 would still be the default). And
I don't
Hi,
Some packages are now distributed with lzma compression instead of bzip2,
e.g. texinfo 4.12:
http://ftp.gnu.org/gnu/texinfo/
Going back to gzip would be a regression, in particular there is a big
size difference (here 2.4 MB for gzip, 1.3 MB for lzma).
What changes does a Portfile need
On 2008-08-04 11:26:12 +0200, Anders F Björklund wrote:
Added as http://trac.macports.org/changeset/38960
To install the lzma program, see port lzmautils.
So, should the port build-depend on lzmautils?
--
Vincent Lefèvre [EMAIL PROTECTED] - Web: http://www.vinc17.org/
100% accessible
On 2008-08-07 15:53:08 -0500, Ryan Schmidt wrote:
The current situation is an inconvenience, but things can be made to
work.
When installing p5-getopt-long (and some others), use the -f flag to
force it to overwrite files from the perl5.{8,10} port.
When upgrading perl, it will
At least 5 ports installed a broken ${prefix}/lib/charset.alias file:
http://trac.macports.org/ticket/11474
http://trac.macports.org/ticket/11968
http://trac.macports.org/ticket/16152
http://trac.macports.org/ticket/17084
Since this seems to be a more or less global problem, shouldn't the
On 2009-02-09 13:10:06 +0100, Rainer Müller wrote:
Ryan Schmidt wrote:
It might be nice if a port could recommend the user install another
port in addition, via some new keyword. For example, graphviz could
recommend the user install graphviz-gui as well. postgresql83 could
On 2009-02-10 09:02:15 -0500, Jeremy Lavergne wrote:
Would running into collisions be easily solved with that we recommend
messages? For example, some program may want PHP +apache2 and another
could want PHP +no_web.
One should never recommend a port with a negative variant. This
does not
There's somthing strange:
$ port cat p5-image-exiftool
# $Id: Portfile 38454 2008-07-21 13:51:06Z bl...@macports.org $
PortSystem 1.0
PortGroup perl5 1.0
perl5.setup Image-ExifTool 7.37
maintainers blair openmaintainer
description Perl interface to EXIF
On 2009-03-08 18:22:46 +0100, Rainer Müller wrote:
Adam Byrtek wrote:
When playing with dependencies for a new port that requires certain
CPAN libraries I found out that there are multiple p5 ports containing
libraries already included in perl5.8. I had this problem with the
following
On 2009-03-09 05:19:35 +, Marcus Calhoun-Lopez wrote:
Vincent Lefevre vincent-opd...@... writes:
On 2009-03-08 18:22:46 +0100, Rainer Müller wrote:
Adam Byrtek wrote:
When playing with dependencies for a new port that requires certain
CPAN libraries I found out
On 2009-03-12 23:22:15 +, Eric Hall wrote:
Again, see /etc/man.conf, in particular the MANSECT line.
But if you're using man from MacPorts, the config file is:
/opt/local/etc/man.conf
--
Vincent Lefèvre vinc...@vinc17.org - Web: http://www.vinc17.org/
100% accessible validated
On 2009-03-16 09:33:18 -0700, Bradley Giesbrecht wrote:
This could be good. Just not have perl5.8 install man pages. If perl
users don't use them why waste effort.
I frequently use the Perl-related man pages. In practice, for
the modules, they give the same information as perldoc (when
the
On 2009-03-16 15:07:19 -0700, Bradley Giesbrecht wrote:
I tried this earlier using
./Configure ... -man1ext=1perl5.8 -man3ext=3perl5.8
I don't think it is a good idea to use a dot in the extension, as
this can be very confusing (this would probably make completion
fail or behave in a strange
On 2009-05-14 14:08:45 -0700, and.dam...@macports.org wrote:
Revision: 50984
http://trac.macports.org/changeset/50984
Author: and.dam...@macports.org
Date: 2009-05-14 14:08:43 -0700 (Thu, 14 May 2009)
Log Message:
---
Maintainer email change, second batch, mail
On 2009-07-14 16:13:46 -0400, Kristofer Henriksson wrote:
As a side note, such divergent error handling makes it a shame that
there is no debug-type option for error handling to be set in
browsers, with XHTML-style failure when debugging is enabled and
silent HTML-style perseverance when
On 2009-07-14 06:58:50 -0400, Jeremy Lavergne wrote:
Future work? I wonder, what were the advantages of going with XHTML
to begin with?
One can use XML tools on it. I sometimes do that on the bug database
to see if I haven't missed anything and so on.
--
Vincent Lefèvre vinc...@vinc17.org -
On 2009-08-05 15:53:17 -0400, Jeremy Lavergne wrote:
I believe one can deactivate emacs 22 and install emacs 23. If a
revert is necessary, deactivate the new version and reactivate the
old one. No need for an extra port that will only be around for a
version.
I meant *without having to
Does MacPorts have a use_xz variable? Some tarballs are now distributed
in both gz and xz compression format, and xz is significantly smaller
than gz. For instance, for the coreutils 7.4:
.tar.gz 9.3 MB
.tar.xz 3.9 MB
--
Vincent Lefèvre vinc...@vinc17.org - Web: http://www.vinc17.org/
On 2009-09-02 01:57:27 -0500, Ryan Schmidt wrote:
They do point out indirectly that not all software supports this
configure argument. For software that doesn't, your solution is
fine. But I would not characterize it as a problem with MacPorts to
be worked around; rather, it's simply a
Hi,
(I've been quite busy these times and still am.)
On 2009-10-14 20:14:54 -0600, Bryan Blackburn wrote:
Note that there really isn't any kind of actionable violation, as MacPorts
uses the BSD license, and the web page there looks to be his own creation...
But is DarwinPorts a trademark? In
On 2009-10-22 13:58:01 -0400, Jeremy Lavergne wrote:
Search for pspp mac and you'll find dp.com sitting at #4 or #5.
This demonstrates at least one way people are finding it: searching
for the open source project they want and mac. In my example,
simply searching for pspp will not being up
On 2009-09-29 09:50:00 +1000, Joshua Root wrote:
If you already have MacPorts installed, the preferred method for
updating is to run:
sudo port selfupdate
On Tiger:
[...]
=== making install in src/programs
=== making install in src/programs/daemondo
mkdir -p build
/usr/bin/install -c -o
On 2009-10-28 08:27:15 +1100, Joshua Root wrote:
Yes, that's http://trac.macports.org/ticket/20760.
Thanks. If it is not fixed in the next version, I think that the
upgrade instructions should mention this bug.
--
Vincent Lefèvre vinc...@vinc17.net - Web: http://www.vinc17.net/
100% accessible
On 2009-12-13 19:52:12 -0600, Ryan Schmidt wrote:
I put the epoch line back in the portfile, because the epoch line
can never be removed from a portfile; the epoch can only ever
increase, otherwise MacPorts will not report the port as being
outdated. I put the epoch line above the version line
With smartmontools @5.39_0+darwin, I can see:
-rwxr-xr-x 2 root admin 404 2010-01-26 23:48:21
/Library/LaunchDaemons/net.sourceforge.smartmontools.smartd.plist
Is it normal that this file is executable?
Similarly, org.freedesktop.avahi-daemon.plist and
org.freedesktop.avahi-dnsconfd.plist are
On 2010-01-26 16:33:01 -0800, Scott Haneda wrote:
On Jan 26, 2010, at 3:14 PM, Vincent Lefevre wrote:
Similarly, org.freedesktop.avahi-daemon.plist and
org.freedesktop.avahi-dnsconfd.plist are also executable.
These are usually symbolic links, and not the actual files.
These ones
Hi,
On 2010-02-06 18:27:12 -0800, mcalh...@macports.org wrote:
Revision: 63519
http://trac.macports.org/changeset/63519
Author: mcalh...@macports.org
Date: 2010-02-06 18:27:10 -0800 (Sat, 06 Feb 2010)
Log Message:
---
gmp: Update version 4.3.2 -- 5.0.1.
[...]
@@
1 - 100 of 128 matches
Mail list logo
