Re: NEW: devel/cmark
On Fri, 10 Aug 2018 14:45:19 +0100 Stuart Henderson wrote: > It's already committed. > Sorry for the noise, i may have not noticed something has gone wrong during the initial tree fetch on this machine :( > On 2018/08/10 15:19, Charlène wrote: > > On Thu, 2 Aug 2018 20:34:36 +0200 > > Jan Klemkow wrote: > > > > > Hi Rafael, > > > > > > On Thu, Aug 02, 2018 at 06:31:53PM +0200, Rafael Sadowski wrote: > > > > On Thu Aug 02, 2018 at 05:36:13PM +0200, Jan Klemkow wrote: > > > > > Hi Rafael, > > > > > > > > > > I also worked on an cmark port. I took your tar ball and > > > > > fixed all comments Stuart pointed out. Just, the MAINTAINER > > > > > field is still unset, But, a portscheck run does not require > > > > > this field. > > > > > > > > > > I replaced the manual DISTFILE and MASTER_SITE handling by the > > > > > GH_* variables, moved it to category "textproc" and correct > > > > > some spacing. > > > > > > > > That wasn't the way to go and the spacing was fine -- trust me > > > > or use vim. Please see my traball. > > > > > > You are right, I missed some spaces. But, I already used vim ;-) > > > > > > > > > > > > > Hopefully that helps you. I also need this tool for a private > > > > > project of mine. > > > > > > > > Would you like to take MAINTAINER? > > > > > > Yes, I can do that. See my attached tar ball. I removed a > > > useless line and replaced some spaces by tabs. And it uses the > > > GH_* variables. > > > > > > Hope that's fine for all so far. > > > > > > Thanks, > > > Jan > > > > Hi! > > > > I'd be happy to see cmark added to ports too. > > > > The build and runtime works fine on i386, i tested old personal > > projects that used it and John Gruber's test suite [1] without any > > issue. > > > > Charlène. > > > > [1] > > http://daringfireball.net/projects/downloads/MarkdownTest_1.0.zip > > > > >
Re: NEW: devel/cmark
It's already committed. On 2018/08/10 15:19, Charlène wrote: > On Thu, 2 Aug 2018 20:34:36 +0200 > Jan Klemkow wrote: > > > Hi Rafael, > > > > On Thu, Aug 02, 2018 at 06:31:53PM +0200, Rafael Sadowski wrote: > > > On Thu Aug 02, 2018 at 05:36:13PM +0200, Jan Klemkow wrote: > > > > Hi Rafael, > > > > > > > > I also worked on an cmark port. I took your tar ball and fixed > > > > all comments Stuart pointed out. Just, the MAINTAINER field is > > > > still unset, But, a portscheck run does not require this field. > > > > > > > > I replaced the manual DISTFILE and MASTER_SITE handling by the > > > > GH_* variables, moved it to category "textproc" and correct some > > > > spacing. > > > > > > That wasn't the way to go and the spacing was fine -- trust me or > > > use vim. Please see my traball. > > > > You are right, I missed some spaces. But, I already used vim ;-) > > > > > > > > > > Hopefully that helps you. I also need this tool for a private > > > > project of mine. > > > > > > Would you like to take MAINTAINER? > > > > Yes, I can do that. See my attached tar ball. I removed a useless > > line and replaced some spaces by tabs. And it uses the GH_* > > variables. > > > > Hope that's fine for all so far. > > > > Thanks, > > Jan > > Hi! > > I'd be happy to see cmark added to ports too. > > The build and runtime works fine on i386, i tested old personal > projects that used it and John Gruber's test suite [1] without any > issue. > > Charlène. > > [1] http://daringfireball.net/projects/downloads/MarkdownTest_1.0.zip > >
Re: NEW: devel/cmark
On Thu, 2 Aug 2018 20:34:36 +0200 Jan Klemkow wrote: > Hi Rafael, > > On Thu, Aug 02, 2018 at 06:31:53PM +0200, Rafael Sadowski wrote: > > On Thu Aug 02, 2018 at 05:36:13PM +0200, Jan Klemkow wrote: > > > Hi Rafael, > > > > > > I also worked on an cmark port. I took your tar ball and fixed > > > all comments Stuart pointed out. Just, the MAINTAINER field is > > > still unset, But, a portscheck run does not require this field. > > > > > > I replaced the manual DISTFILE and MASTER_SITE handling by the > > > GH_* variables, moved it to category "textproc" and correct some > > > spacing. > > > > That wasn't the way to go and the spacing was fine -- trust me or > > use vim. Please see my traball. > > You are right, I missed some spaces. But, I already used vim ;-) > > > > > > > Hopefully that helps you. I also need this tool for a private > > > project of mine. > > > > Would you like to take MAINTAINER? > > Yes, I can do that. See my attached tar ball. I removed a useless > line and replaced some spaces by tabs. And it uses the GH_* > variables. > > Hope that's fine for all so far. > > Thanks, > Jan Hi! I'd be happy to see cmark added to ports too. The build and runtime works fine on i386, i tested old personal projects that used it and John Gruber's test suite [1] without any issue. Charlène. [1] http://daringfireball.net/projects/downloads/MarkdownTest_1.0.zip
Re: NEW: devel/cmark
On 2018/08/02 20:34, Jan Klemkow wrote: > Hi Rafael, > > On Thu, Aug 02, 2018 at 06:31:53PM +0200, Rafael Sadowski wrote: > > On Thu Aug 02, 2018 at 05:36:13PM +0200, Jan Klemkow wrote: > > > Hi Rafael, > > > > > > I also worked on an cmark port. I took your tar ball and fixed all > > > comments Stuart pointed out. Just, the MAINTAINER field is still unset, > > > But, a portscheck run does not require this field. > > > > > > I replaced the manual DISTFILE and MASTER_SITE handling by the GH_* > > > variables, moved it to category "textproc" and correct some spacing. > > > > That wasn't the way to go and the spacing was fine -- trust me or use > > vim. Please see my traball. > > You are right, I missed some spaces. But, I already used vim ;-) > > > > > > > Hopefully that helps you. I also need this tool for a private project > > > of mine. > > > > Would you like to take MAINTAINER? > > Yes, I can do that. See my attached tar ball. I removed a useless line > and replaced some spaces by tabs. And it uses the GH_* variables. > > Hope that's fine for all so far. > > Thanks, > Jan DISTNAME isn't needed here, the one generated from GH_PROJECT and GH_TAGNAME is good anyway. OK sthen@
Re: NEW: devel/cmark
Hi Rafael, On Thu, Aug 02, 2018 at 06:31:53PM +0200, Rafael Sadowski wrote: > On Thu Aug 02, 2018 at 05:36:13PM +0200, Jan Klemkow wrote: > > Hi Rafael, > > > > I also worked on an cmark port. I took your tar ball and fixed all > > comments Stuart pointed out. Just, the MAINTAINER field is still unset, > > But, a portscheck run does not require this field. > > > > I replaced the manual DISTFILE and MASTER_SITE handling by the GH_* > > variables, moved it to category "textproc" and correct some spacing. > > That wasn't the way to go and the spacing was fine -- trust me or use > vim. Please see my traball. You are right, I missed some spaces. But, I already used vim ;-) > > > > Hopefully that helps you. I also need this tool for a private project > > of mine. > > Would you like to take MAINTAINER? Yes, I can do that. See my attached tar ball. I removed a useless line and replaced some spaces by tabs. And it uses the GH_* variables. Hope that's fine for all so far. Thanks, Jan cmark.tar.gz Description: Binary data
Re: NEW: devel/cmark
Hi Rafael,
I also worked on an cmark port. I took your tar ball and fixed all
comments Stuart pointed out. Just, the MAINTAINER field is still unset,
But, a portscheck run does not require this field.
I replaced the manual DISTFILE and MASTER_SITE handling by the GH_*
variables, moved it to category "textproc" and correct some spacing.
Hopefully that helps you. I also need this tool for a private project
of mine.
bye,
Jan
On Thu, Aug 02, 2018 at 10:41:30AM +0100, Stuart Henderson wrote:
> On 2018/08/02 11:03, Rafael Sadowski wrote:
> > please find attached a small dependency for the upcoming
> > multimedia/mkvtoolnix update. All tests are passed on amd64.
> >
> > pkg_info:
> > Information for inst:cmark-0.28.3
> >
> > Comment:
> > CommonMark parsing and rendering library and program in C
> >
> > Required by:
> > mkvtoolnix-25.0.0-no_x11
> >
> > Description:
> > cmark is the C reference implementation of CommonMark, a rationalized
> > version
> > of Markdown syntax with a spec.
> >
> > Maintainer: The OpenBSD ports mailing-list
> >
> > WWW: https://commonmark.org/
> >
> > Ok? Comments?
>
> textproc or converters would seem better than devel?
Fixed.
> $ cat distinfo
> SHA256 (0.28.3.tar.gz) = rMmGhdPBtRX/eHrHyZQYja2vKKLXAMEMEiHaQZm64fw=
> SIZE (0.28.3.tar.gz) = 229391
>
> Please rename that to something sensible via the DISTFILES=...{...} mechanism.
This is also fixed.
cmark.tar.gz
Description: Binary data
Re: NEW: devel/cmark
On 2018/08/02 18:31, Rafael Sadowski wrote: > On Thu Aug 02, 2018 at 05:36:13PM +0200, Jan Klemkow wrote: > > Hi Rafael, > > > > I also worked on an cmark port. I took your tar ball and fixed all > > comments Stuart pointed out. Just, the MAINTAINER field is still unset, > > But, a portscheck run does not require this field. > > > > I replaced the manual DISTFILE and MASTER_SITE handling by the GH_* > > variables, moved it to category "textproc" and correct some spacing. > > That wasn't the way to go and the spacing was fine -- trust me or use > vim. Please see my traball. Oh I missed the /archive/ URL, I thought it was in /releases/ (assumed you would have just used GH_* if it was /archive/). GH_* _is_ the way to go for /archive/.
Re: NEW: devel/cmark
On Thu Aug 02, 2018 at 05:36:13PM +0200, Jan Klemkow wrote:
> Hi Rafael,
>
> I also worked on an cmark port. I took your tar ball and fixed all
> comments Stuart pointed out. Just, the MAINTAINER field is still unset,
> But, a portscheck run does not require this field.
>
> I replaced the manual DISTFILE and MASTER_SITE handling by the GH_*
> variables, moved it to category "textproc" and correct some spacing.
That wasn't the way to go and the spacing was fine -- trust me or use
vim. Please see my traball.
>
> Hopefully that helps you. I also need this tool for a private project
> of mine.
Would you like to take MAINTAINER?
>
> bye,
> Jan
>
> On Thu, Aug 02, 2018 at 10:41:30AM +0100, Stuart Henderson wrote:
> > On 2018/08/02 11:03, Rafael Sadowski wrote:
> > > please find attached a small dependency for the upcoming
> > > multimedia/mkvtoolnix update. All tests are passed on amd64.
> > >
> > > pkg_info:
> > > Information for inst:cmark-0.28.3
> > >
> > > Comment:
> > > CommonMark parsing and rendering library and program in C
> > >
> > > Required by:
> > > mkvtoolnix-25.0.0-no_x11
> > >
> > > Description:
> > > cmark is the C reference implementation of CommonMark, a rationalized
> > > version
> > > of Markdown syntax with a spec.
> > >
> > > Maintainer: The OpenBSD ports mailing-list
> > >
> > > WWW: https://commonmark.org/
> > >
> > > Ok? Comments?
> >
> > textproc or converters would seem better than devel?
>
> Fixed.
Yes, I'm fine with textproc makes more sense then devel.
>
> > $ cat distinfo
> > SHA256 (0.28.3.tar.gz) = rMmGhdPBtRX/eHrHyZQYja2vKKLXAMEMEiHaQZm64fw=
> > SIZE (0.28.3.tar.gz) = 229391
> >
> > Please rename that to something sensible via the DISTFILES=...{...}
> > mechanism.
>
> This is also fixed.
All comments packed in the new tarball.
cmark-0.28.3p0.tar.gz
Description: Binary data
Re: NEW: devel/cmark
On 2018/08/02 11:03, Rafael Sadowski wrote:
> Hi All.
>
> please find attached a small dependency for the upcoming
> multimedia/mkvtoolnix update. All tests are passed on amd64.
>
> pkg_info:
> Information for inst:cmark-0.28.3
>
> Comment:
> CommonMark parsing and rendering library and program in C
>
> Required by:
> mkvtoolnix-25.0.0-no_x11
>
> Description:
> cmark is the C reference implementation of CommonMark, a rationalized version
> of Markdown syntax with a spec.
>
> Maintainer: The OpenBSD ports mailing-list
>
> WWW: https://commonmark.org/
>
>
> Ok? Comments?
textproc or converters would seem better than devel?
$ cat distinfo
SHA256 (0.28.3.tar.gz) = rMmGhdPBtRX/eHrHyZQYja2vKKLXAMEMEiHaQZm64fw=
SIZE (0.28.3.tar.gz) = 229391
Please rename that to something sensible via the DISTFILES=...{...} mechanism.
