.\" $Id: TODO.mdoc,v 1.61 2004/07/04 19:28:28 jmmv Exp $
.\"
.\" buildtool
.\" Copyright (c) 2002, 2003, 2004 Julio M. Merino Vidal
.\"
.\" Redistribution and use in source and binary forms, with or without
.\" modification, are permitted provided that the following conditions
.\" are met:
.\" 1. Redistributions of source code must retain the above copyright
.\"    notice, this list of conditions and the following disclaimer.
.\" 2. Redistributions in binary form must reproduce the above copyright
.\"    notice, this list of conditions and the following disclaimer in
.\"    the documentation and/or other materials provided with the
.\"    distribution.
.\" 3. Neither the name of the author nor the names of contributors may
.\"    be used to endorse or promote products derived from this software
.\"    without specific prior written permission.
.\"
.\" THIS SOFTWARE IS PROVIDED BY THE AUTHOR AND CONTRIBUTORS ``AS IS''
.\" AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED
.\" TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A
.\" PARTICULAR PURPOSE ARE DISCLAIMED.  IN NO EVENT SHALL THE AUTHOR
.\" OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL,
.\" SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT
.\" LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF
.\" USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
.\" ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY,
.\" OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT
.\" OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
.\" SUCH DAMAGE.
.\"/
.ds volume-operating-system
.ds volume-ds-1 Buildtool Distribution Information
.Dd July 4, 2004
.Dt TODO 1
.Os BSD
.
.Sh NAME
.
.Nm TODO
.Nd List of things to be done before Buildtool 1.0 is ready
.
.Sh INTRODUCTION
.
Before Buildtool 1.0 can be released, there are lots of things to do.
This file tries to list some of them (not all), so you can get an idea
about where we want to go.
If you feel you can help developing some of these items (or providing
design ideas), please tell us.
.Pp
Each module is detailed in its own section. Todo items are in no
special order.
.
.Sh COMMON
.
.Bl -bullet
.It
Fix bugs, of course. ;-)
.It
Make scripts use the new
.Sq global
keyword in bt_sh, to the extent that
.Fl w
shows no warnings.
.It
Verify Cygwin support (mainly test if it works and add support for .exe
extensions).
.It
Rewrite the testsuite; it's useless as it's now.
It should provide regression tests for almost all features provided by
Buildtool.
.El
.
.Sh MODULE SPECIFIC
.
.
.Ss bt_config
.
.Bl -bullet
.It
Improve shared library support.
Currently checks rely on system's name; this is okay for some details
but we need checks for compiler specific stuff.
.It
More automated checks, for common programs, headers, and libraries.
Ideally, a non-trivial program (I have pkgsrc's bootstrap system in mind)
has to be converted to see which useful checks are missing, compared to
GNU autoconf.
.It
Now that bt_sh has the isfunc command, we can implement real support
for multiple languages (avoiding the
.Sq current language
hack, probably).
.El
.
.Ss bt_dist
.
.Bl -bullet
.It
An idea: add binary targets like DEB or RPM.
I will not add this myself as I have no knowledge of how these files
work.
If anybody is interested in adding this, contact me.
.El
.
.Ss bt_doc
.
.Bl -bullet
.It
None planned.
.El
.
.Ss bt_lint
.
.Bl -bullet
.It
Add more checks, as Buildtool standards are developed.
.It
Implement support for other kind of standards (like The GNU
Standards), using a variable in the defs file to indicate it.
.El
.
.Ss bt_logic
.
.Bl -bullet
.It
Just an idea: create compiler wrappers during the configuration stage (like
pkgsrc's buildlink does).
This may make parsing of options faster as some conditions can be decided
during configuration time (i.e., just once), and also may make portability
easier (i.e., a different wrapper for each compiler).
.El
.
.Ss bt_pkgflags
.
.Bl -bullet
.It
Deprecate pkgflags file support (anyone using that?  I doubt it).
It's starting to look stupid to try to force people use a new format,
because pkgconfig files are already doing a good job (when written
correctly).
Therefore, pkgconfig support needs to be reviewed and improved in this
module before this can happen.
.El
.
.Ss bt_sh
.
.Bl -bullet
.It
None planned.
.El
.
.Ss bt_swcgen
.
.Bl -bullet
.It
None planned.
.El
.
.Ss bt_wizard
.
.Bl -bullet
.It
Add more questions to tune the resulting output files.
.El
.\" Local Variables: ***
.\" mode: nroff ***
.\" End: ***
.\" vim: syntax=nroff