On 2020/06/04 22:28, Alex Free wrote:
> Does everything look ok on the email I sent to ports?
>
> https://marc.info/?l=openbsd-ports=159123552330253=2
Not had time to look closely yet. I think the | characters in PERMIT_*
are a problem. And please just send a tar.gz not a diff for new ports
> Sent: Wednesday, June 03, 2020 at 4:05 PM
> From: "Stuart Henderson"
> To: "Alex Free"
> Cc: "Renaud Allard" , ports@openbsd.org
> Subject: Re: does a new port have to be the latest version?
>
> On 2020/06/03 14:58, Alex Free wrote:
> &g
On 6/3/20 2:11 PM, Stuart Henderson wrote:
On 2020/06/03 13:54, Alex Free wrote:
What is the program?
CDIrip, the current GitHub is at https://github.com/jozip/cdirip .
yes 0.6.3 looks to be a bit of a step backwards there. looking at the diff
it did also remove a duplicate write of
> Just saying "released under GPL" without doing other steps isn't enough.
> It needs at least a copyright line with a license grant somewhere
> preferably on each file, that's why the license goes to some lengths to
> explain how to do it.
>
> Also releasing some version under GPL doesn't mean
On 2020/06/03 14:58, Alex Free wrote:
> > Sent: Wednesday, June 03, 2020 at 2:24 PM
> > From: "Stuart Henderson"
> > To: "Renaud Allard"
> > Cc: ports@openbsd.org
> > Subject: Re: does a new port have to be the latest version
> > > Note that it doesn't have proper licensing so will need to be marked as
> > > PERMIT_PACKAGE/PERMIT_DISTFILES=no license (some mention of "version
> > > developed on sourceforge under gpl" isn't a valid license grant).
> > >
> > https://github.com/jozip/cdirip/blob/master/LICENSE
> >
> >
> Sent: Wednesday, June 03, 2020 at 2:24 PM
> From: "Stuart Henderson"
> To: "Renaud Allard"
> Cc: ports@openbsd.org
> Subject: Re: does a new port have to be the latest version?
>
> On 2020/06/03 14:17, Renaud Allard wrote:
> >
> >
> &g
On 2020/06/03 14:17, Renaud Allard wrote:
>
>
> On 6/3/20 2:11 PM, Stuart Henderson wrote:
> > On 2020/06/03 13:54, Alex Free wrote:
> > > >
> > > > What is the program?
> > > >
> > >
> > > CDIrip, the current GitHub is at https://github.com/jozip/cdirip .
> > >
> >
> > yes 0.6.3 looks to
On 2020/06/03 13:54, Alex Free wrote:
> >
> > What is the program?
> >
>
> CDIrip, the current GitHub is at https://github.com/jozip/cdirip .
>
yes 0.6.3 looks to be a bit of a step backwards there. looking at the diff
it did also remove a duplicate write of though.
Note that it doesn't have
>
> What is the program?
>
CDIrip, the current GitHub is at https://github.com/jozip/cdirip .
On 2020/06/03 11:33, ale...@mail.com wrote:
> I am working on my first port, and version 0.6.3 broke big endian
> support. The software’s latest version is still broken on big endian.
> The reason for this is stated in the change log as removing endian
> specific code. The software compiles fine
> > Version 0.6.2 works on big endian, which is what I’ll be using this
> > software on a lot.
> If you worked on a 0.6.2 port and 0.6.3 gets out before your port
> submission, this is by no means any blocker.
>
This isn’t the case. 0.6.2 was released in 2002 and the latest version
in 2018.
> I guess this depend of the port and how old the release you want to
> include is. For a network daemon it's better if it's up to date but for
> a game or non network tool, I think it's possible to have an older
> version.
>
Well that’s good news. Version 0.6.2 is from 2002. Version 0.6.3 is
On Wed, Jun 03, 2020 at 11:33:08AM +0200, ale...@mail.com wrote:
> I am working on my first port, and version 0.6.3 broke big endian
> support. The software’s latest version is still broken on big endian.
> The reason for this is stated in the change log as removing endian
> specific code. The
On Wed, 3 Jun 2020 11:33:08 +0200
ale...@mail.com:
> I am working on my first port, and version 0.6.3 broke big endian
> support. The software’s latest version is still broken on big endian.
> The reason for this is stated in the change log as removing endian
> specific code. The software
I am working on my first port, and version 0.6.3 broke big endian
support. The software’s latest version is still broken on big endian.
The reason for this is stated in the change log as removing endian
specific code. The software compiles fine but does not function
correctly, giving errors.
16 matches
Mail list logo
