Re: unix(3lua)
On Fri, May 18, 2018 at 12:20:20AM +0100, Alexander Nasonov wrote: > David Holland wrote: > > On Thu, May 17, 2018 at 03:41:26PM +0200, Marc Balmer wrote: > > > One more thing: When we imported Lua into base, we very clearly > > > decided that pkgsrc Lua and base Lua should be two separate things. > > > Base Lua can not use pkgsrc Lua modules by default (and most > > > probably vice versa). > > > > ...you very clearly decided; some of the rest of us consider that a > > bug. > > Bug??? I thought a clear separation between the base and packages > was a selling point of all BSDs. pkgsrc uses builtin things all the time, even when they're objectively worse and pkgsrc has an alternative, like not shipping its own compiler for older releases, base tar which dumps garbage PosixHeaders.1234 crap and breaks random programs like octave-forge, base openssl past EOL, etc.
Re: unix(3lua)
Oops, adding others in > On 17 May 2018, at 13:15, Sevan Janiyanwrote: > > > >> On 17 May 2018, at 13:02, Martin Husemann wrote: >> >> Is there any reason to import it? Why not pkgsrc? > > Because the functionality is there in base already, it's just another > representation of a small subset of it (Lua) as opposed to new foreign > functionality and it's a good starting point for covering the rest of our > system libraries. > > > Sevan
Re: unix(3lua)
On Thu, May 17, 2018 at 12:55:26PM +0100, Sevan Janiyan wrote: > I would like to import this into base as unix(3lua) and wanted to ask > for feedback, is there any reason not to? Is there any reason to import it? Why not pkgsrc? Martin
Re: unix(3lua)
> Am 17.05.2018 um 13:55 schrieb Sevan Janiyan: > > Hello, > There is a unixlua[1] module which is a Lua binding for some the > functions in our C libraries in base as well as system calls. The code > base is small and doesn't have any tentacles (a hand full of C files, > excluding headers), It's licensed under a 3 clause style BSD license and > written by mbalmer@. > I would like to import this into base as unix(3lua) and wanted to ask > for feedback, is there any reason not to? > Keep in mind that we already have some NetBSD/Unix specific modules in base, like GPIO access or an sqlite module (e,g, to dig stuff from nan pages). This module complements what we already have and makes Lua in base generally more useful. Plus it is easy to extend if needed. If the license (3-clause) is of concern, it can be changed to whatever is preferred. So I'd say, yes please Sevan, go ahead an committ it. ok mbalmer@ if you want.
unix(3lua)
Hello, There is a unixlua[1] module which is a Lua binding for some the functions in our C libraries in base as well as system calls. The code base is small and doesn't have any tentacles (a hand full of C files, excluding headers), It's licensed under a 3 clause style BSD license and written by mbalmer@. I would like to import this into base as unix(3lua) and wanted to ask for feedback, is there any reason not to? Sevan [1] https://github.com/arcapos/luaunix
Re: unix(3lua)
One more thing: When we imported Lua into base, we very clearly decided that pkgsrc Lua and base Lua should be two separate things. Base Lua can not use pkgsrc Lua modules by default (and most probably vice versa). The "unix" module is important doe the Lua subsystem in NetBSD's base, because without such a module, you can not write real software in Lua. Lua's own "os" module is limited to what ANSI C provides, which is not really much. > Am 17.05.2018 um 15:37 schrieb Marc Balmer: > > This belongs into base because it works with base Lua. It is meant to > enhance the general Lua experience in NetBSD. > > > >> Am 17.05.2018 um 14:02 schrieb Martin Husemann : >> >> On Thu, May 17, 2018 at 12:55:26PM +0100, Sevan Janiyan wrote: >>> I would like to import this into base as unix(3lua) and wanted to ask >>> for feedback, is there any reason not to? >> >> Is there any reason to import it? Why not pkgsrc? >> >> Martin >
Re: unix(3lua)
On Thu, May 17, 2018 at 03:41:26PM +0200, Marc Balmer wrote: > One more thing: When we imported Lua into base, we very clearly > decided that pkgsrc Lua and base Lua should be two separate things. > Base Lua can not use pkgsrc Lua modules by default (and most > probably vice versa). ...you very clearly decided; some of the rest of us consider that a bug. -- David A. Holland dholl...@netbsd.org
Re: unix(3lua)
David Holland wrote: > On Thu, May 17, 2018 at 03:41:26PM +0200, Marc Balmer wrote: > > One more thing: When we imported Lua into base, we very clearly > > decided that pkgsrc Lua and base Lua should be two separate things. > > Base Lua can not use pkgsrc Lua modules by default (and most > > probably vice versa). > > ...you very clearly decided; some of the rest of us consider that a > bug. Bug??? I thought a clear separation between the base and packages was a selling point of all BSDs. -- Alex