nix config next steps
So now that we have some code to play with, we need to keep the process
moving. The next step is to start documenting the changes, including
in the standard euphoria documentation, but also we need to write a
man page.
Is there anyone interested in starting the man page? I'd say that we probably
want to make a single page to cover exu/ecu/backendu/bind/shroud.*
Then we need to start working on packaging. There are two main package
formats that are probably worth targeting. I run a Debian based system,
so I'm mostly interested in building a .deb package, but I'm guessing we
have some RPM users around here, as well.
I've started looking over the Debian policy manual, and some docs about
creating .deb packages. It's certainly not a trivial task to do it
correctly (meaning in a sufficient state that it might be included in
the Debian distribution) which I think everyone would agree should be
a goal of this project.
Any feedback/assistance is encouraged and appreciated.
Matt
* Are names like backendu, bind and shroud too generic? Assuming that the
ultimate goal is to get accepted into Linux distributions, do these conflict
with anything already out there? Should we change them? If so, to what?
|
Not Categorized, Please Help
|
|
