Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Maintenance plan #18

Open
GoogleCodeExporter opened this issue Jul 1, 2015 · 1 comment
Open

Maintenance plan #18

GoogleCodeExporter opened this issue Jul 1, 2015 · 1 comment

Comments

@GoogleCodeExporter
Copy link

Recently I asked dn.smelov for a write access to help with maintenance of ozex. 
Here're things I'd like to do:

* Elaborate/clean up wiki
* Apply some patches for better error checking and logging
* Elaborate startup script and config file
* Switch to GNU Makefile as the default one
* Allow to build against system dependency libs

After that, work towards git migration and using swampex as standalone 
dependency lib, not code-duplicated within each project using it.



Original issue reported on code.google.com by pmis...@gmail.com on 19 Mar 2011 at 10:24

@GoogleCodeExporter
Copy link
Author

Could you please tell more about these items:

* Apply some patches for better error checking and logging

Some more details on this?

* Elaborate startup script and config file

Format of the config file and library used to implement it?

* Allow to build against system dependency libs

Which build technology are you going to use - autoconf/automake or something 
else?

Original comment by dmitry.a...@gmail.com on 19 Mar 2011 at 12:36

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant