On Tuesday, December 15, 2015, Ryan Schmidt wrote:
>
> > On Dec 15, 2015, at 5:40 PM, ebori...@macports.org wrote:
> >
> > Revision
> > 143618
> > Author
> > ebori...@macports.org
> > Date
> > 2015-12-15 15:40:40 -0800 (Tue, 15 Dec 2015)
> > Log Message
> >
> > py-htmldocs: Remove 25, add 35. U
Yes, when I originally added it, I assumed files would be stored in a directory
based on ${version}, but it turned out they were storing them in a directory
based on ${branch}. I couldn't tell at the time because branch and version were
equal. Anyway, the goal is to avoid redirects and to ensure
On Dec 15, 2015, at 6:10 PM, Bradley Giesbrecht wrote:
> Perhaps patchfiles could take a path as a value?
>
> patchfiles patch-current.diff
> patchfiles patch-relative-to-filespath.diff
> patchfiles /why/would/we/want/this/patch-full-path.diff
>
> I should have check first, does patchfiles alre
On Dec 15, 2015, at 6:28 PM, Joshua Root wrote:
>> Revision: 143598
>> https://trac.macports.org/changeset/143598
>> Author: petr at macports.org
>> Date: 2015-12-15 10:21:49 -0800 (Tue, 15 Dec 2015)
>> Log Message:
>> ---
>> py-ckanapi: minor edit to trigger py35 build
>
> On Dec 15, 2015, at 5:40 PM, ebori...@macports.org wrote:
>
> Revision
> 143618
> Author
> ebori...@macports.org
> Date
> 2015-12-15 15:40:40 -0800 (Tue, 15 Dec 2015)
> Log Message
>
> py-htmldocs: Remove 25, add 35. Update download / regex checks. Set license
> to restrictive to avoid having
On 2015-12-16 13:24 , David Evans wrote:
> On 12/15/15 4:30 PM, Joshua Root wrote:
>>> Revision: 143602
>>> https://trac.macports.org/changeset/143602
>>> Author: devans at macports.org
>>> Date: 2015-12-15 10:48:47 -0800 (Tue, 15 Dec 2015)
>>> Log Message:
>>> ---
>>> ports
On 12/15/15 4:30 PM, Joshua Root wrote:
>> Revision: 143602
>> https://trac.macports.org/changeset/143602
>> Author: devans at macports.org
>> Date: 2015-12-15 10:48:47 -0800 (Tue, 15 Dec 2015)
>> Log Message:
>> ---
>> ports with perl variants: increment revision to reset d
> Revision: 143602
> https://trac.macports.org/changeset/143602
> Author: devans at macports.org
> Date: 2015-12-15 10:48:47 -0800 (Tue, 15 Dec 2015)
> Log Message:
> ---
> ports with perl variants: increment revision to reset default variant to
> +perl5_22.
What do you me
> Revision: 143598
> https://trac.macports.org/changeset/143598
> Author: petr at macports.org
> Date: 2015-12-15 10:21:49 -0800 (Tue, 15 Dec 2015)
> Log Message:
> ---
> py-ckanapi: minor edit to trigger py35 build
You don't need to modify the file to trigger a build, you
> On Dec 15, 2015, at 4:10 PM, Bradley Giesbrecht wrote:
>
> Perhaps patchfiles could take a path as a value?
>
> patchfiles patch-current.diff
> patchfiles patch-relative-to-filespath.diff
Whoops:
patchfiles somedir/patch-relative-path.diff
> patchfiles /why/would/we/want/this/patch-full-path
Perhaps patchfiles could take a path as a value?
patchfiles patch-current.diff
patchfiles patch-relative-to-filespath.diff
patchfiles /why/would/we/want/this/patch-full-path.diff
I should have check first, does patchfiles already work this way?
Regards,
Bradley Giesbrecht (pixilla)
> On Dec
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 12/15/15 9:02 AM, Ryan Schmidt wrote:
>
>> On Dec 15, 2015, at 12:11 AM, dev...@macports.org wrote:
>>
>> Revision
>> 143573
>> Author
>> dev...@macports.org
>> Date
>> 2015-12-14 22:11:59 -0800 (Mon, 14 Dec 2015)
>> Log Message
>>
>> p5-extutils-f77: update to version 1.19.
>
>> --- trunk/dpo
> On Dec 15, 2015, at 12:11 AM, dev...@macports.org wrote:
>
> Revision
> 143573
> Author
> dev...@macports.org
> Date
> 2015-12-14 22:11:59 -0800 (Mon, 14 Dec 2015)
> Log Message
>
> p5-extutils-f77: update to version 1.19.
> --- trunk/dports/perl/p5-extutils-f77/files/patch-F77.pm.diff 2015-1
On Tuesday December 15 2015 10:17:58 Daniel J. Luke wrote:
> Anything is possible, although this seems like a bad idea to me.
I agree it could lead to lots of problems when wielded in the wrong hands (so
it might be better to use a dedicated utility rather than the port command
itself).
> Mayb
On 12/15/15 6:52 AM, petr wrote:
>
> The update to gsl @2.1 seems to have broken binary compatibility with
> dependent ports. So they need to be revision bumped. I see this for `nco` and
> `qgis` but there are very probably more. See below.
>
> ~petr
>
>
> {{{
> [...]
> ---> Installing gsl
On Dec 15, 2015, at 7:39 AM, René J.V. Bertin wrote:
> Would it be possible to implement a mechanism allowing this, so that one
> could use something along the lines of
>
> %> port execute foo.tcl
>
> and, by extension, put `#!/usr/bin/env port execute` in the file's 1st line?
Anything is pos
The update to gsl @2.1 seems to have broken binary compatibility with dependent
ports. So they need to be revision bumped. I see this for `nco` and `qgis` but
there are very probably more. See below.
~petr
{{{
[...]
---> Installing gsl @2.1_0
---> Cleaning gsl
---> Removing work directory
Hi,
As a port maintainer it happens that I need to act on data (that I normally [=
in Portfiles] obtain through procedures and/or a PortGroup) outside of the
regular port configure/build/etc phases. This happens most often when I need to
update a series of (sub)ports, like at the moment (KF5 Fr
20 matches
Mail list logo
