Lua for sysinst, next steps?

[Marc Balmer]

So we have a working diff for Lua support in sysinst that allows Lua to
be disabled on a per platform basis if floppies overflow.

So what should be the next steps? There are probably (hopefully...)
some folks around that want to step in and help with coding, so that
would mean to commit it, but then are of course as always those that say
"please don't commit until it is finished and polished" ;) So I am
stalled now.

Open for suggestions. Personally I don't like to have diffs lying
around for too long, especially since it means that I don't work a lot
on them (I work on different computers and thus like the comfort of
accessing a repository instead of moving around diffs, imo cvs is here
for development ;)

[Brett Lymn]

Post by Marc Balmer
Open for suggestions. Personally I don't like to have diffs lying
around for too long, especially since it means that I don't work a lot
on them (I work on different computers and thus like the comfort of
accessing a repository instead of moving around diffs, imo cvs is here
for development ;)

Create a branch. That is what a branch is for - do experimental/major
work on that can/may be merged back to trunk at a later date. People
who are interested can then check the branch out and help.

[Marc Balmer]

Post by Brett Lymn

Post by Marc Balmer
Open for suggestions. Personally I don't like to have diffs lying
around for too long, especially since it means that I don't work a lot
on them (I work on different computers and thus like the comfort of
accessing a repository instead of moving around diffs, imo cvs is here
for development ;)

Create a branch. That is what a branch is for - do experimental/major
work on that can/may be merged back to trunk at a later date. People
who are interested can then check the branch out and help.

Thank your for your feedback.

This is neither experimental (in production use since years) nor a major
work, but something affecting a single binary only. We will for sure
not create a branch for this, but continue our work on the -current branch.

[Brett Lymn]

Post by Marc Balmer
This is neither experimental (in production use since years)

That is good to know.

Post by Marc Balmer
nor a major
work, but something affecting a single binary only.

Right but it is the gateway binary to NetBSD - a first time user uses it
to install the system. We need to make sure it is in a fit state at
release time.

Post by Marc Balmer
We will for sure
not create a branch for this, but continue our work on the -current branch.

Please consider a branch if you think that what you are going to do may
leave sysinst in an unusable state for extended periods.

[Marc Balmer]

Post by Brett Lymn

Post by Marc Balmer
This is neither experimental (in production use since years)

That is good to know.

Post by Marc Balmer
nor a major
work, but something affecting a single binary only.

Right but it is the gateway binary to NetBSD - a first time user uses it
to install the system. We need to make sure it is in a fit state at
release time.

I totally agree on this.

Post by Brett Lymn

Post by Marc Balmer
We will for sure
not create a branch for this, but continue our work on the -current branch.

Please consider a branch if you think that what you are going to do may
leave sysinst in an unusable state for extended periods.

Yes. The intent, however, is not to break sysinst for even a short period.

[Thor Lancelot Simon]

Post by Brett Lymn
Create a branch. That is what a branch is for - do experimental/major
work on that can/may be merged back to trunk at a later date. People
who are interested can then check the branch out and help.

What he said.

Thor

[Marc Balmer]

I am sure you already read my reply to that email.

Freundliche Grüsse,
Marc Balmer
--
Marc Balmer
micro systems, Landstrasse 66, CH-5073 Gipf-Oberfrick
Tel.: [phone], http://www.msys.ch/
arcapos(r) Kassensystem: http://www.arcapos.ch/

Post by Thor Lancelot Simon

Post by Brett Lymn
Create a branch. That is what a branch is for - do experimental/major
work on that can/may be merged back to trunk at a later date. People
who are interested can then check the branch out and help.

What he said.
Thor

[Martin Husemann]

Post by Marc Balmer
So what should be the next steps? There are probably (hopefully...)
some folks around that want to step in and help with coding, so that
would mean to commit it, but then are of course as always those that say
"please don't commit until it is finished and polished" ;) So I am
stalled now.

I don't see why this shouldn't be commited - it basically is a complete
first phase (not sure what other polishing would be needed), and you can
deal with further phases on a branch.

Martin

[Marc Balmer]

Post by Martin Husemann

Post by Marc Balmer
So what should be the next steps? There are probably (hopefully...)
some folks around that want to step in and help with coding, so that
would mean to commit it, but then are of course as always those that say
"please don't commit until it is finished and polished" ;) So I am
stalled now.

I don't see why this shouldn't be commited - it basically is a complete
first phase (not sure what other polishing would be needed), and you can
deal with further phases on a branch.

Thank you. Yes it is complete and it is working, we are using it in
production for years.

We will, however, not put this into a branch, the -current branch is
fine for this kind of development. It concerns a single binary only ans
we want this to be exposed to current-users to get feedback.

[Izumi Tsutsui]

Post by Martin Husemann

Post by Marc Balmer
So what should be the next steps? There are probably (hopefully...)
some folks around that want to step in and help with coding, so that
would mean to commit it, but then are of course as always those that say
"please don't commit until it is finished and polished" ;) So I am
stalled now.

I don't see why this shouldn't be commited - it basically is a complete
first phase (not sure what other polishing would be needed), and you can
deal with further phases on a branch.

If we can disable sysinst Lua support by USE_LUA=no, I think it's okay
to commit to head. I could also help to fix possible Tier-II breakage.
(unless buildability persons complain daily failure)

But if we can provide test install images/isos with Lua enabled sysinst
(by "build.sh release install-image iso-image" or so) before commit
it will also help reviewers.

---
Izumi Tsutsui