[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#1012286: RFS: zig/0.9.1-1 [ITP] -- Programming language



Hi,

quick progress report.

* Nick Hastings <nicholaschastings@gmail.com> [220615 14:20]:
> 
> * Adam Borowski <kilobyte@angband.pl> [220603 23:34]:
> > On Fri, Jun 03, 2022 at 09:38:37AM +0900, Nick Hastings wrote:
> > 
> > Worst news first: the copyright file requires a lot more work.  I see for
> > example unlisted Khronos stuff (lib/libc/include/any-windows-any/{GL,KHR}/),
> > NTP (lib/libc/include/any-linux-any/linux/timex.h), Zope (mingw), ISC,
> > Apache, APSL, ...  And the list of copyright holders is even more
> > incomplete.  This is a big honking waste of time but it's
> > required... :(
> 
> I actually already put quite a bit of effort into the copyright file,
> but it has been a very long time since I last worked on it.
> 
> Taking a quick look now I wonder if maybe I have overlooked include
> directories, perhaps assuming that anything in there would be covered by
> src directories. Or maybe I'd just become burned out with it and wanted
> to move on!
> 
> Anyway I think I'm ready to dive back in.

The initial copyright file was generated by debmake, have since used
decopy which seems to have found a lot of things that were previously
missed. I'm slowly grinding though it, adding and fixing things. It's
very time consuming, but I'm making progress.

https://github.com/NickHastings/zig-debian/blob/decopy/copyright

> > The package includes a bunch of tests, and with the likelihood of code not
> > handling a particular arch, glibc, etc, I'd say it's a must to run
> > them.
> 
> Ok, I'll investigate running the tests.

I've added the tests to debian/rules. However two of them fail. See
https://github.com/NickHastings/zig-debian/blob/tests/rules

It's unclear to me if they are important. Have asked on zig irc, but so
far, no response. Will try to chase it up soon.

> > Not a strict requirement, but a man page would be greatly appreciated.
> 
> Will put it on the todo list, but hopefully I can get upstream to do
> something on that front.

This is still sitting untouched at the bottom of the todo list.

Cheers,

Nick.


Reply to: