Petr,
1) it is a trivial install -- just download and extract -- so
hopefully it's not a big issue. We can always move it into a variant.
2) Spyder has a menu link to go to python documentation, which I patch
to go to the installed documentation. (hence the dependency.)
- Eric
On Tue, Dec 15, 2
Hi Eric,
why does py-spyder{,-devel} actually depend (library dependency) on
py-htmldocs. I understand that the py??-htmldocs provides the respective python
documentation, so why would I need it as dependency of a python
module/application? I think py-spyder{,-devel} to do so.
Thanks for the
On Jan 23, 2015, at 11:49 AM, Michael Dickens wrote:
>
> On Tue, Jan 20, 2015, at 02:17 PM, Lawrence Velázquez wrote:
>> The depspec is interpreted as a regular expression (with some caveats),
>> not a glob. For instance, my HandBrake WIP portfile contains this:
>>
>>depends_build port
On Tue, Jan 20, 2015, at 02:26 PM, René J.V. Bertin wrote:
> I suppose you're not supporting any random swig version, so how about
> doing what the python Portfile itself does, a foreach over a list of
> known versions? swig-python and swig-python-devel both don't install a
> single common file?
I
On Tue, Jan 20, 2015, at 02:17 PM, Lawrence Velázquez wrote:
> The depspec is interpreted as a regular expression (with some caveats),
> not a glob. For instance, my HandBrake WIP portfile contains this:
>
> depends_build port:autoconf \
> port:automake \
>
On Tuesday January 20 2015 12:25:32 Michael Dickens wrote:
> but that's ugly & cumbersome. There has got to be a better way. Any
> advice on a robust yet concise way to do this? Thanks! - MLD
Hi Michael,
I suppose you're not supporting any random swig version, so how about doing
what the python
ecause we don't know the SWIG version. For example, something like:
> {{{
> depends-build-append path:share/swig/*/python:swig-python
> }}}
> where the "*" is actually the SWIG version string (e.g., "3.0.4"). I
> could just have SWIG install into "${pre
I've been working on getting a "swig-devel" port up and running, and it
works locally for me. But in order to use it (e.g.,
"swig-python-devel"), I need to specify dependencies using a wildcard
because we don't know the SWIG version. For example, something like:
{{{
d
If B and C are different versions of the same program, for example a stable
version and a development version, then it is usual to use a path:-style
dependency. The ports should be named X and X-devel. The ports would install
the same files to the same places and would be marked as conflicting
On Oct 18, 2014, at 7:10 PM, Ryan Schmidt wrote:
>>>>
>>>>> On Oct 18, 2014, at 1:41 PM, Mark Brethen wrote:
>>>>>>
>>>>>> Is it possible to specify e.g lib-depends {port:A || port:B} i.e. either
>>>>>> port A or por
2014, at 1:41 PM, Mark Brethen wrote:
>>>>>
>>>>> Is it possible to specify e.g lib-depends {port:A || port:B} i.e. either
>>>>> port A or port B?
>>>>
>>>> No, unless port A and port B are different versions of the same s
On Oct 18, 2014, at 7:19 PM, Ryan Schmidt wrote:
>
> On Oct 18, 2014, at 7:16 PM, Mark Brethen wrote:
>>
>> On Oct 18, 2014, at 7:10 PM, Ryan Schmidt wrote:
>>
>>> On Oct 18, 2014, at 1:41 PM, Mark Brethen wrote:
>>>>
>>>> Is it p
On Oct 18, 2014, at 7:16 PM, Mark Brethen wrote:
>
> On Oct 18, 2014, at 7:10 PM, Ryan Schmidt wrote:
>
>> On Oct 18, 2014, at 1:41 PM, Mark Brethen wrote:
>>>
>>> Is it possible to specify e.g lib-depends {port:A || port:B} i.e. either
>>> port A or
On Oct 18, 2014, at 7:10 PM, Ryan Schmidt wrote:
>
> On Oct 18, 2014, at 1:41 PM, Mark Brethen wrote:
>>
>> Is it possible to specify e.g lib-depends {port:A || port:B} i.e. either
>> port A or port B?
>
> No, unless port A and port B are different vers
On Oct 18, 2014, at 1:41 PM, Mark Brethen wrote:
>
> Is it possible to specify e.g lib-depends {port:A || port:B} i.e. either port
> A or port B?
No, unless port A and port B are different versions of the same software that
install their files to the same locations.
For example, if
You'd have it also share the variants/subport naming.
There's a portgroup for ensuring whether variants are selected:
https://trac.macports.org/browser/trunk/dports/_resources/port1.0/group/active_variants-1.1.tcl
On Oct 18, 2014, at 3:13 PM, Mark Brethen wrote:
> Right, but I have subport C who
On Oct 18, 2014, at 2:09 PM, Jeremy Lavergne wrote:
> Usually a variant or subport would achieve this.
>
> On Oct 18, 2014, at 2:41 PM, Mark Brethen wrote:
>
>> Is it possible to specify e.g lib-depends {port:A || port:B} i.e. either
>> port A or port B?
>
Right,
Is it possible to specify e.g lib-depends {port:A || port:B} i.e. either port A
or port B?
Mark
___
macports-dev mailing list
macports-dev@lists.macosforge.org
https://lists.macosforge.org/mailman/listinfo/macports-dev
Sharing Clemens nice reply with the dev list.
On Sep 15, 2012, at 2:11 PM, Clemens Lang wrote:
>> Do you know how port keeps track of non-port dependencies like path:,
>> lib: or bin:?
>>
>> Example: depends_lib path:bin/mysql_config5:mysql5
>>
>> Looking in regiestry.db I see the dependencies
On Feb 19, 2010, at 15:09, matthias.ram...@googlemail.com wrote:
> I've been working on bringing the aged editors/abiword port up to date. One
> problem I have encountered is that it needs the +quartz variant of cairo to
> compile. As there still seems to be no way to declare such a dependency,
Hello,
I've been working on bringing the aged editors/abiword port up to date. One problem I
have encountered is that it needs the +quartz variant of cairo to compile. As there still
seems to be no way to declare such a dependency, how should I proceed? Is there a
"best practice" for this case
Good point, the reinplaces will fail
Scapy 2 is now a Framework, and actually needs to be installed,
whereas 1.2 was just a single python file.
This goes back to my suggestion to have a new scapy2 port
Mike
On Jul 29, 2009, at 8:16 AM, MacPorts wrote:
#18156: scapy still depends on Python
On Sat, 2009-07-04 at 06:01 +, MacPorts wrote:
> #18306: automoc requires apple-gcc42 depends-build
> --+-
> Reporter: j...@… | Owner: illogic...@…
> Type: defect|
On May 13, 2009, at 12:59, Jeremy Lavergne wrote:
If a port uses Qt 4, should I provide variants for which qt4 (kde,
mac, x11) it uses?
qt4-kde exists only because kde ports are currently incompatible with
qt4 4.5. So qt4-kde was created for version 4.4. Presumably if your
port is a kde
If a port uses Qt 4, should I provide variants for which qt4 (kde,
mac, x11) it uses?
smime.p7s
Description: S/MIME cryptographic signature
___
macports-dev mailing list
macports-dev@lists.macosforge.org
http://lists.macosforge.org/mailman/listinfo.
And pylons 0.9.6.1 and the too.
http://trac.macosforge.org/projects/macports/ticket/14235
On 2/13/08, js <[EMAIL PROTECTED]> wrote:
> Maintainer,
>
> This is the reminder for the ticket which hasn't received no response
> from maintainers more than 72 hours.
> http://trac.macosforge.org/projects
It seems that no-one answered:
On 2007-02-07 12:55:47 +0100, Vincent Lefevre wrote:
> 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 s
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:
stardict
28 matches
Mail list logo
