On Jan 17, 2008, at 1:30 AM, Joshua Root wrote:
I've made a patch for those and attached it to ticket #12913. I
used the dependency style suggested by Ryan.
https://trac.macosforge.org/projects/macports/ticket/12913
Has someone mailed the maintainers of the other affected ports?
I just
On Thu, Jan 17, 2008 at 05:30:12PM +1100, Joshua Root wrote:
I've made a patch for those and attached it to ticket #12913. I used the
dependency style suggested by Ryan.
https://trac.macosforge.org/projects/macports/ticket/12913
Has someone mailed the maintainers of the other affected
Simon Ruderich wrote:
I just checked which ports are using TeTeX. Quite a few.
Nomaintainer:
[...]
I've made a patch for those and attached it to ticket #12913. I used the
dependency style suggested by Ryan.
https://trac.macosforge.org/projects/macports/ticket/12913
Has someone mailed the
Le 14 janv. 08 à 23:32, Simon Ruderich a écrit :
- [EMAIL PROTECTED]: dvipdfmx
dvipdfmx is provided by texlive_base, but it's an older version that
actually crashes when doing some operations.
Paul
___
macports-dev mailing list
Citando Ryan Schmidt :
I hoped someone else would have something to say on the topic, since I
myself don't use any of this TeX software. But they haven't so I will.
I have something to say.
On Jan 9, 2008, at 18:03, John Owens wrote:
Ryan Schmidt [EMAIL PROTECTED] writes:
If more than one
Citando Ryan Schmidt :
On Jan 14, 2008, at 03:18, Emmanuel Hainry wrote:
At the moment, what dependent ports will check for is a texmf tree
(provided by texlive_texmf-minimal and some binaries (latex, pdflatex,
mktexlsr...). So the best dependency scheme would probably be
bin:latex:texlive.
On Jan 14, 2008, at 03:18, Emmanuel Hainry wrote:
If more than one port installs a binary foo, and either one is
good enough, this could be specified in a portfile by saying
depends_lib path:${prefix}/bin/foo:bar
where bar is the preferred port for providing foo if it is not
already
On Jan 14, 2008, at 4:18 AM, Emmanuel Hainry wrote:
I am the maintainer of the texlive package (with openmaintainer) and
since the port exists, the only bugs reported were does not compile
in
leopard (which is now solved) and a lex file is not understood by
macports' lex on ppc (which was
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
I hoped someone else would have something to say on the topic, since
I myself don't use any of this TeX software. But they haven't so I will.
On Jan 9, 2008, at 18:03, John Owens wrote:
Ryan Schmidt [EMAIL PROTECTED] writes:
If more than one port installs a binary foo, and either one is
Ryan Schmidt wrote:
- Let's say I'm updating a port and want to make this change.
How can I actually tell what file is the dependency (without
delving into the makefiles)? Seems like I'd have to delve.
Personally, I would just pick any important file (a binary perhaps, or
a library) that
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
Howdy, new committer here, happy to be on board!
For several years I've been using tetex successfully.
But as it's no longer updated, I'm happy to move to
the new texlive port.
It was tricky to install texlive because of tetex
(getting tetex deactivated and texlive activated
was ugly).
But more
On Jan 9, 2008, at 17:48, John Owens wrote:
For several years I've been using tetex successfully.
But as it's no longer updated, I'm happy to move to
the new texlive port.
It was tricky to install texlive because of tetex
(getting tetex deactivated and texlive activated
was ugly).
But more
14 matches
Mail list logo
