Re: [macports-ports] branch master updated: atf: update to 0.21

[Ryan Schmidt]

On Mar 2, 2018, at 01:58, Ken wrote:

> +github.setupjmmv atf 0.21
> +
> +# github.tarball_from downloads or releases does not set the mastersite 
> correctly
> +master_sites
> https://github.com/jmmv/atf/releases/download/${name}-${version}/

It does if you set the tag prefix. See:

https://github.com/macports/macports-ports/commit/c998339ff1ecd76f4e428efe8725083451f570f1

Re: [macports-ports] branch master updated: atf: update to 0.21

[Ryan Schmidt]

On Mar 2, 2018, at 01:58, Ken wrote:

> Ken (kencu) pushed a commit to branch master
> in repository macports-ports.
> 
> 
> https://github.com/macports/macports-ports/commit/1677db90e20bc989731a2614ca659ecbb54b3b0c
> 
> The following commit(s) were added to refs/heads/master by this push:
> 
>  new 1677db9  atf: update to 0.21
> 
> 1677db9 is described below
> 
> 
> commit 1677db90e20bc989731a2614ca659ecbb54b3b0c
> 
> Author: Ken Cunningham
> AuthorDate: Thu Mar 1 23:56:22 2018 -0800
> 
> 
> atf: update to 0.21
> 
> 
> 
> change to github
> 
> add license
> 
> remove xmlcatmgr dep which appears no longer needed
> 
> ---
>  devel/atf/Portfile | 21 ++---
>  1 file changed, 10 insertions(+), 11 deletions(-)

> +license netbsd

This is not a license MacPorts knows:

"atf" is not distributable because its license "netbsd" is not known to be 
distributable

Is this different from the BSD license?

Re: Upgrading Pandoc

[Mark Anderson]

Thanks everyone. I hadn't seen that ticket - I've been experimenting with
Haskell and boy getting it to run IS magic. Writing a parser, super easy.
Compiling it? That's a pain.

—Mark
___
Mark E. Anderson 

On Wed, Mar 7, 2018 at 6:35 PM, Clemens Lang  wrote:

> Hi,
>
> On Sun, Mar 04, 2018 at 02:18:24PM -0500, Mark Anderson wrote:
> > So I started trying to move pandoc from some older version to 2.1.1
> > but then I realized I needed to upgrade the Haskell compiler and
> > libraries to do that. I got started, but wow, this is something else.
> > Does anyone have tips about upgrading Haskell?
>
> I'm attaching my current progress as a patch. It should apply cleanly to
> the current master.
>
> I didn't package stack. It has way too many dependencies to get this
> done without automation, and unless somebody picks up
> https://github.com/neverpanic/cabal2port (or re-writes a similar tool
> from scratch), that's not happening.
>
> Current state of this patch is that I'd need to commit this together
> with a revbump of every haskell port (because otherwise the libraries
> installed by these ports link against libraries built against the old
> GHC, which will not work). That's probably simple enough, so if you want
> to prepare a PR with my changes + the revbumps, that'd be welcome.
>
> Of course, somebody would also have to test build this (or at least some
> large and important haskell ports).
>
> > Is there a magic to it or should I just keep slogging along and open a
> > ticket?
>
> It's magic, unfortunately. ;-)
>
> --
> Clemens
>

Re: Upgrading Pandoc

[Clemens Lang]

Hi,

On Sun, Mar 04, 2018 at 02:18:24PM -0500, Mark Anderson wrote:
> So I started trying to move pandoc from some older version to 2.1.1
> but then I realized I needed to upgrade the Haskell compiler and
> libraries to do that. I got started, but wow, this is something else.
> Does anyone have tips about upgrading Haskell?

I'm attaching my current progress as a patch. It should apply cleanly to
the current master.

I didn't package stack. It has way too many dependencies to get this
done without automation, and unless somebody picks up
https://github.com/neverpanic/cabal2port (or re-writes a similar tool
from scratch), that's not happening.

Current state of this patch is that I'd need to commit this together
with a revbump of every haskell port (because otherwise the libraries
installed by these ports link against libraries built against the old
GHC, which will not work). That's probably simple enough, so if you want
to prepare a PR with my changes + the revbumps, that'd be welcome.

Of course, somebody would also have to test build this (or at least some
large and important haskell ports).

> Is there a magic to it or should I just keep slogging along and open a
> ticket?

It's magic, unfortunately. ;-)

-- 
Clemens
diff --git a/_resources/port1.0/group/haskell-1.0.tcl 
b/_resources/port1.0/group/haskell-1.0.tcl
index df8e404d4c..58db42cca8 100644
--- a/_resources/port1.0/group/haskell-1.0.tcl
+++ b/_resources/port1.0/group/haskell-1.0.tcl
@@ -53,7 +53,7 @@ set haskell.compiler_list {ghc}
 # updates.
 array set haskell.compiler_configuration {
 ghc {port   ghc
- version7.8.3
+ version8.0.1
  compiler   ${prefix}/bin/ghc
  ghc-pkg${prefix}/bin/ghc-pkg}
 }
diff --git a/devel/haskell-platform/Portfile b/devel/haskell-platform/Portfile
index b10f76a316..ab814572f3 100644
--- a/devel/haskell-platform/Portfile
+++ b/devel/haskell-platform/Portfile
@@ -5,7 +5,7 @@ PortSystem  1.0
 namehaskell-platform
 
 if {$subport == $name} {
-version 2014.2.0.0
+version 8.0.1
 categories  devel haskell
 maintainers cal openmaintainer
 description \
@@ -117,9 +117,9 @@ proc haskell_platform_tool {pkgname pkgversion pkgrevision 
{block {}}} {
 # Additional Platform Libraries #
 #
 
-haskell_platform_port async 2.0.1.5 1 {
-checksums   rmd160  0ec360bc373c4ca0b3c7617ec611f2414804e9cd \
-sha256  
cd13ac558f4f63e567100805770648e89307a3210852b17038c9be4fcc3aa83c
+haskell_platform_port async 2.1.0 0 {
+checksums   rmd160  6b82f7ecc2b76b795b3a75860f741556b977e830 \
+sha256  
93c37611f9c68b5cdc8cd9960ae77a7fbc25da83cae90137ef1378d857f22c2f
 
 depends_lib-append  port:hs-stm
 
@@ -137,11 +137,12 @@ haskell_platform_port async 2.0.1.5 1 {
 automatically killed when their parent dies (see withAsync).
 }
 
-haskell_platform_port attoparsec 0.10.4.0 4 {
-checksums   rmd160  1fc9845e60fb0cddc9ffa8838c446b3046cd3522 \
-sha256  
b6b84e0dbd1c3beec1dedea578ac2f4d62afbe66b383582b7b3349406866d346
+haskell_platform_port attoparsec 0.13.0.2 0 {
+checksums   rmd160  9785e4716309332b659d2b789cac4bbf7d48 \
+sha256  
69f7f381f644ba4a6f348bbff9b2b4280b7b602e8e25e59eadb6e30ad5f2ec6a
 
-depends_lib-append  port:hs-text
+depends_lib-append  port:hs-text \
+port:hs-scientific
 
 description Fast combinator parsing for bytestrings and text
 long_description\
@@ -150,9 +151,9 @@ haskell_platform_port attoparsec 0.10.4.0 4 {
 formats.
 }
 
-haskell_platform_port case-insensitive 1.1.0.3 1 {
-checksums   rmd160  351ebf0ae84c4c580b910dbd3ed0828b309874c7 \
-sha256  
7b255fe63155d53ab84b248ab5ba9306fd4bec47a6198e3275cf9cb41c4d263b
+haskell_platform_port case-insensitive 1.2.0.6 0 {
+checksums   rmd160  bc4b78cc1c8e812ea243453f26e0bb4697d68d96 \
+sha256  
bc7b53517fefc475311bfe6dbab8ade47ab8df11a59079653aa3271e9ffcb1c4
 
 depends_lib-append  port:hs-hashable \
 port:hs-text
@@ -165,9 +166,9 @@ haskell_platform_port case-insensitive 1.1.0.3 1 {
 insensitive to cases.
 }
 
-haskell_platform_port fgl 5.5.0.1 1 {
-checksums   rmd160  c6c1f89db51d8d3ce6687dab13109c7f40c9c10c \
-sha256  
aa61664ba38db3e54124b702b1ee92a72a569c981b759e48cfb567078b038763
+haskell_platform_port fgl 5.5.2.3 0 {
+checksums   rmd160  8371f511eadac788974737f0fad7ec157eadc4b3 \
+sha256  
f4113b5221917feb6389494bf8b7b6221ee00f322b6c25fc25a25795549f9e20
 
 depends_lib-append  port:hs-mtl
 
@@ -175,21 +176,17 @@ haskell_platform_port fgl 5.5.0.1 1 {
 

Re: [macports-infrastructure] branch master updated: Use mpbb to mirror distfiles

[Ryan Schmidt]

On Mar 7, 2018, at 11:24, Rainer Müller wrote:

> On 2018-03-07 18:21, Rainer Müller wrote:
>> This should probably use path_jobs here. These are identical paths at
>> the moment, but I think it is better to keep the abstraction.
> 
> Nevermind, I was interrupted while typing the mail and you already fixed
> it by now. Sorry for the noise.

But thanks for the review. I haven't been checking my email...

Re: [macports-infrastructure] branch master updated: Use mpbb to mirror distfiles

[Rainer Müller]

On 2018-03-07 18:21, Rainer Müller wrote:
> This should probably use path_jobs here. These are identical paths at
> the moment, but I think it is better to keep the abstraction.

Nevermind, I was interrupted while typing the mail and you already fixed
it by now. Sorry for the noise.

Rainer

Re: [macports-infrastructure] branch master updated: Use mpbb to mirror distfiles

[Rainer Müller]

On 2018-03-07 16:03, Ryan Schmidt wrote:
> Ryan Schmidt (ryandesign) pushed a commit to branch master
> in repository macports-infrastructure.
>
> https://github.com/macports/macports-infrastructure/commit/7a2fc5596970826f362413b362a5a3dc23db5e7a
>
> The following commit(s) were added to refs/heads/master by this push:
> new 7a2fc55 Use mpbb to mirror distfiles 7a2fc55 is described below
>
> commit 7a2fc5596970826f362413b362a5a3dc23db5e7a Author: Ryan Schmidt 
> 
> AuthorDate: Wed Mar 7 09:03:01 2018 -0600
>
> Use mpbb to mirror distfiles ---
>  buildbot/config.json.sample |  3 +++
>  buildbot/master.cfg | 32 +---
>  2 files changed, 32 insertions(+), 3 deletions(-)
>
> diff --git a/buildbot/config.json.sample b/buildbot/config.json.sample
> index d500efb..55d9508 100644 --- a/buildbot/config.json.sample +++
> b/buildbot/config.json.sample @@ -36,6 +36,9 @@  "sshkeyfile": "",
>  "sshknownhostsfile": "ssh_known_hosts",
>  "destpath": ""
> + }, + "mirror": { + "distfilesdir": "",  }
>  }
>  }
> diff --git a/buildbot/master.cfg b/buildbot/master.cfg index
> 8c9e9bb..a05fa07 100644 --- a/buildbot/master.cfg +++
> b/buildbot/master.cfg @@ -678,11 +678,37 @@ if 'portindex' in
> config['deploy']:  
>  if 'mirror' in config['deploy']:
>  jobs_mirror_factory = util.BuildFactory()
> + + # get mpbb; we'll do the checkout of base and dports via these
> scripts + jobs_mirror_factory.addStep(GitForTools( +
> repourl=config['mpbburl'], + progress=True, + env={'PATH': path_ports},
This should probably use path_jobs here. These are identical paths at
the moment, but I think it is better to keep the abstraction.

Rainer

Re: request for port create command, to build a portfile from a URL

[Rainer Müller]

On 2018-03-07 11:32, Enrico Maria Crisostomo wrote:
> This is a little bit offtopic IMHO, anyway: I found surprising too that
> the github portgroup was not documented, given the high percentage of
> software that I build out of github repositories, and that's why I
> recently contributed the documentation of the github portgroup:
> 
> https://github.com/macports/macports-guide/pull/12
> 
> It has been merged some days ago. Yet, I don't see it online yet.

That is because we still have not any automatic deployment on
build.macports.org for any of our websites. I am irregularly running
these jobs from my local buildbot setup on my personal MacBook every few
weeks, which is the only reason they are not completely outdated.

I triggered another run of these jobs, so these changes should be
available shortly online.

Rainer

Re: Port submission for aidadoc

[G Alexander]

-H

> On Mar 7, 2018, at 03:24, Ryan Schmidt  wrote:
> 
> 
>> On Mar 7, 2018, at 00:43, G Alexander wrote:
>> 
>> I'd set a no cache flag so you don't get lots of cookie and cache garbage
> 
> Huh?
> 

Re: Port submission for aidadoc

[Ryan Schmidt]

On Mar 7, 2018, at 00:43, G Alexander wrote:

> I'd set a no cache flag so you don't get lots of cookie and cache garbage

Huh?

Re: request for port create command, to build a portfile from a URL

[G Alexander]

I play in a different playground and primarily use either master, dev or 
develop branches as I run with latest codebase available.  ffmpeg, imagemagick, 
opencv, clang6, openblas, etc.  These get a lot of PRs everyday. 

Having to update the Portfiles manually with latest hash and date/version is 
not optimal.  

Why can't a script find the repo, verify hash and date automatically then 
archive or if you have a GitHub account verify your SSH, and just grab the repo 
without creating an archive.

> On Mar 7, 2018, at 02:32, Enrico Maria Crisostomo 
>  wrote:
> 
> This is a little bit offtopic IMHO, anyway: I found surprising too that the 
> github portgroup was not documented, given the high percentage of software 
> that I build out of github repositories, and that's why I recently 
> contributed the documentation of the github portgroup:
> 
> https://github.com/macports/macports-guide/pull/12
> 
> It has been merged some days ago. Yet, I don't see it online yet.
> 
>> On 7 Mar 2018, at 11:29, db  wrote:
>> 
>>> On 7 Mar 2018, at 01:53, Rainer Müller  wrote:
 On 2018-03-06 23:00, db wrote:
 [...] an *overview* of how to write a portfile is much needed.
>>> Isn't this what this chapter in the guide is supposed to provide?
>>> https://guide.macports.org/#development
>> 
>> Yes, supposed. When you're in it's difficult to say, but AFAIR I was 
>> probably trying to write a portfile for something hosted on GitHub without 
>> knowing about the relative portgroup and its documentation being buried 
>> somewhere under the prefix in the tcl file itself.
> 

Re: request for port create command, to build a portfile from a URL

[Enrico Maria Crisostomo]

This is a little bit offtopic IMHO, anyway: I found surprising too that the 
github portgroup was not documented, given the high percentage of software that 
I build out of github repositories, and that's why I recently contributed the 
documentation of the github portgroup:

https://github.com/macports/macports-guide/pull/12 


It has been merged some days ago. Yet, I don't see it online yet.

> On 7 Mar 2018, at 11:29, db  wrote:
> 
> On 7 Mar 2018, at 01:53, Rainer Müller  wrote:
>> On 2018-03-06 23:00, db wrote:
>>> [...] an *overview* of how to write a portfile is much needed.
>> Isn't this what this chapter in the guide is supposed to provide?
>> https://guide.macports.org/#development
> 
> Yes, supposed. When you're in it's difficult to say, but AFAIR I was probably 
> trying to write a portfile for something hosted on GitHub without knowing 
> about the relative portgroup and its documentation being buried somewhere 
> under the prefix in the tcl file itself.

Re: request for port create command, to build a portfile from a URL

[db]

On 7 Mar 2018, at 01:53, Rainer Müller  wrote:
> On 2018-03-06 23:00, db wrote:
>> [...] an *overview* of how to write a portfile is much needed.
> Isn't this what this chapter in the guide is supposed to provide?
> https://guide.macports.org/#development

Yes, supposed. When you're in it's difficult to say, but AFAIR I was probably 
trying to write a portfile for something hosted on GitHub without knowing about 
the relative portgroup and its documentation being buried somewhere under the 
prefix in the tcl file itself.