Citando Jack Howarth :
On Fri, Jan 21, 2011 at 05:25:46PM -0800, Bradley Giesbrecht wrote:
Putting your local repository ahead of rsync in sources.conf provides a
valuable method of preventing software from being upgraded.
That would be a valuable method if MacPorts had the version
I never used conflicts. How does it work? And what does it do? I
would expect that if you choose a variant, it will prevent any
conflicting variant to be selected. From your first remark, I gather
it is not the case.
As I said earlier, variants, I can write (and conflicts, I will
add), but tcl
Citando Rainer Müller :
Hi,
the following ports declare a dependency on python_select:
$ port echo dependentof:python_select
glib2
rubber
swig-python
No port should ever declare a dependency on python_select, as this does
*not* pull in any python
That was exactly my goal. Yes I
Citando Rainer Müller :
On 07/05/2010 11:46 AM, Emmanuel Hainry wrote:
Which means? When you install python_select and no python, the symlink
goes to the system's python.
Which would be against our policy that we are using our own libs and do
not rely on the system.
For example
Isn't it redundant with py26-eyed3?
Citando rmsfis...@macports.org :
Revision: 65637
http://trac.macports.org/changeset/65637
Author: rmsfis...@macports.org
Date: 2010-03-29 06:11:51 -0700 (Mon, 29 Mar 2010)
Log Message:
---
audio/eyeD3 new port, a Python module and
Citando ryandes...@macports.org :
Revision: 65227
http://trac.macports.org/changeset/65227
Author: ryandes...@macports.org
Date: 2010-03-23 21:10:34 -0700 (Tue, 23 Mar 2010)
Log Message:
---
moreutils: use a patchfile instead of reinplaces which can break in
Citando Jeremy Lavergne :
Your proposal sounds reasonable to me; that is a very similar approach to
what Ubuntu (debian) takes, and I think it works fine.
I really wish texlive would do what miktex does and use a package manager for
each individual package. but oh well. Their collections
Citando Scott Haneda :
Unfortunately, no, in my research, that is not the case. One of the
very best things that could be done, would be for MacPorts to have
every maintainer of every port contact the developer of that
software, and ask for al link.
I have done this for every port I
Citando Andrea D'Amore :
On 09/set/09, at 09:14, Ryan Schmidt wrote:
I meant a meta-port that would ensure either the MacPorts texlive
port or an external TeX is installed.
I understood it but I don't really know what binaries does a latex
installation rely on, I was asking for
Citando Ryan Schmidt :
On Sep 14, 2009, at 08:01, Jack Howarth wrote:
Coming from working with fink for all these years, the first thing
that struck me was how painful it is in MacPorts to visually
scan through the various Portfiles. In fink, if you are looking
for coding examples of
Citando Dan Ports :
On Thu, Sep 03, 2009 at 01:32:42PM -0500, Ryan Schmidt wrote:
Because we want to allow MacTeX installed outside of MacPorts to
satisfy the dependency. This is an exception to the usual rule,
because TeX is hard to build and the MacPorts TeX ports tend to lag
far
lib:libXm:openmotif
}
--
Emmanuel Hainry
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.cgi/macports-dev
Citando Joshua Root :
Panther has been unsupported since 1.6.0 (as per the 2-latest-releases
policy), and we're basically just continuing to provide dmgs for it
because someone happens to have an machine with it installed and 1.7.1
still builds there without any special coercion. If this is
Citando Shreevatsa R :
On Wed, Mar 25, 2009 at 12:51 AM, Ryan Schmidt ryandes...@macports.org
wrote:
Variants frequently don't get tested when ports are updated, so things break
without the maintainer realizing it.
Exactly! I am glad there is some consensus on this point, although
Citando Jeremy Lavergne :
I was perusing Arch's website today and noticed there's a flag package
out-of-date link when you're viewing information about a package. Is
this something we might find worthwhile for MacPorts since not everything
has a livecheck?
I presume it can put a
Citando Jean-Michel Pouré :
On Sun, 2009-02-01 at 17:40 -0600, Ryan Schmidt wrote:
See my bug reports. I cleaned and rebuilt texlive_base and it failed in
the end. My macport installation is up to date. x86. I don't care about
texlive_base, I am only interested in not breaking ffmpeg-devel.
Citando Joshua Root :
Ian Grant wrote:
Dear List,
Is there a way to specify a port is dependent on a certain revision (and
version!) of another port?
Sadly, no. I forget if there's a ticket specifically for this, but it's
definitely on the to-do list along with
Citando Ryan Schmidt :
On Jun 23, 2008, at 11:07, [EMAIL PROTECTED] wrote:
Revision: 37793
http://trac.macosforge.org/projects/macports/changeset/37793
Author: [EMAIL PROTECTED]
Date: 2008-06-23 09:07:32 -0700 (Mon, 23 Jun 2008)
Log Message:
---
fix install
Citando Jordan K. Hubbard :
[ Making another futile attempt to use a more descriptive subject line ]
On Apr 2, 2008, at 3:56 PM, Rainer Müller wrote:
I think it is a horrible idea. It totally defeats the feature of
having multiple versions of a port but only one active version.
Not at
Citando js :
On Feb 7, 2008 1:58 PM, Ryan Schmidt [EMAIL PROTECTED] wrote:
I think -devel is better.
For one thing, it's more intuitive.
It was proposed that -devel ports should be updated to the latest
stable version, if the latest stable version is newer than the latest
Citando Anders F Björklund :
Guido Soranzio wrote:
Currently there is no official python interpreter for MacPorts
(in the past there was a link to python2.3 even when python24
was installed, IIRC) but many Python programs (or their shebang lines)
expect a python command in the PATH,
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
Citando Juan Manuel Palacios :
On Dec 19, 2007, at 6:35 PM, Anders F Björklund wrote:
Hello guys! It's time to submit 1.6.0 to third party sites advertising
for us.
Don't forget to advertise on darwinports.com :-)
--anders
I'm sure that'll happen on its own, some kind of
Citando Randall Wood :
On 12/1/07, Ryan Schmidt [EMAIL PROTECTED] wrote:
I wouldn't make this generalization. There are ports, like
ImageMagick, that have a +no_x11 variant, which I believe should
continue to have them. ImageMagick can build with support for some
X11 things, or not. By
Citando James Berry :
I just checked in some code (r31491:31492) that supplies and installs spec
files for the /etc/paths.d and /etc/manpaths.d directories if they are
present, as they are on Leopard.
I thought macports was supposed not to mess with anything outside
/opt/local. (apart from
Citando [EMAIL PROTECTED] :
Revision: 30964
http://trac.macosforge.org/projects/macports/changeset/30964
Author: [EMAIL PROTECTED]
Date: 2007-11-12 05:54:05 -0800 (Mon, 12 Nov 2007)
Log Message:
---
Put rubber in category tex
Added Paths:
---
Dear list,
Using Edd Barrett's work for providing a texlive package for openbsd
and the porting guide he wrote
http://students.dec.bmth.ac.uk/ebarrett/texlive/, I made a protfile for
texlive for macports that I just committed to svn. This port works for
me but has not been thoroughly
Citando Ryan Schmidt :
Oh, and: shouldn't all those patches be in the files directory? :)
Oops, Moving them.
By the way, is there a command for that other than for f in patch*; do
svn mv $f files; done as svn mv patch* files/ doesnt work?
By the way, as I explain in another mail, those
Citando Rainer Müller :
Emmanuel Hainry wrote:
Being a simple maintainer, I would say that dependencies on specific
version (à la debian this software require thingy version 2.2.17 but
it is not going to be installed) would make me unable to manage
seriously my ports.
Why? I just
Citando Yves de Champlain :
Hi
I'm doing some tests with gtk-quartz. Many hours of genuine delight
garanteed.
Now, gtk-quartz does not need Xft2 and xrender. So I made the quartz
variant remove those deps. But port upgrade will try to install them
anyway. So I thought of this. I
Citando N_Ox :
Hello,
As the recent discussions on this list concluded, each port should enable
by default most of the features common user may want.
Another thing i believe would be good is that lib ports with doxygen
documentation should have a doc variant that build it.
But, one thing
Citando Simon Ruderich :
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Now I checked it with other installed ports. It seems there are some
problems with livecheck.
No, those are not problems. It is a feature (called defaulting to
something that makes sense in general but may fail).
On 09 Jul 2007, at 14:46, Simon Ruderich wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ryan Schmidt wrote:
I think you're saying that you have a port that installs a
configuration
file, and that you've then changed the configuration file, and
when you
upgrade the port, your
Citando Ryan Schmidt :
Though, I still find it odd that I have to use sudo. If I don't:
$ 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
Citando Charlie Allom :
On Sat, May 19, 2007 at 03:40:48PM +0200, N_Ox wrote:
Hello,
I've just taken over zsh-devel port and one thing seems idiot to me:
What if there is a macports update and that i want to update the
autocompletion port command file? I'd have to do a new
Citando Yves de Champlain :
Hi
Example (the story is real, only the versions numbers have been
changed) :
port upgrade gtk2
...
port installed :
gtk2 2.10.4
gtk2 2.10.8 (active)
port uninstall inactive :
can't uninstall gtk2 2.10.4 because gimp2 depends on
I have noticed that most variants add or delete a configure flag
in the form of --enable-*/--disable-*/--with-*/--without-* and maybe
add or delete a related dependency.
:
: Therefore, I propose that all variants should fit the following
forms:
:
: {en|dis}able_package: If a ported
38 matches
Mail list logo
