>From an acopost perspective, I think the structure that is now in place
is fine. With respect to what I usually do when I can decide what to do,
the only difference is that scripts are now in /bin instead of /src/scripts.
On 30/05/2013 14:31, Tiago Tresoldi wrote:
> In reply to both Ulrik and Giulio
> /bin -- the compiled programs (do you think it is better to have them in
> /src?) and the user scripts, with their extensions removed (using, at
> least for now, the Perl ones)
I think compiled programs should stay where autoconf/automake decides to
put them by default: I do not see any benefit in changing that default.
I usually compile software managed with autotools out-of-tree, often
cross-compiling for several architectures:
BASE_SOURCE=`pwd`
mkdir -p "$BASE_SOURCE"/acopost-<arch>
../configure --prefix=<installation_path> <other_options>
make -j <processor_numbers>
make -j <processor_numbers> check
DESTIDIR=`pwd`/binaries make -j <processor_numbers> install
And the result is that both scripts and binaries end up into
acopost-<arch>/binaries/<installation_path>/bin
> /doc -- nothing changes
I agree.
> /data -- default files (tbt and et rules)
> /data/{language} -- pre-trained models, such as Marco Baroni's Italian
> and Ulrik's pre-1948 Danish; as a complete set of trained models is not
> complex, everything should ideally be kept in a single directory
I like the name /examples, because it makes it clear they are just
examples. Unless we are planning to release data as well. In this case I
think we should setup a sub-module for data and separate clearly data
from software.
> /maintain -- development&debug scripts, C testing, etc.
> /maintain/data -- data for testing, fake language corpus and eventually
> its pre-trained models, etc.
In my opinion we should put in /maintain what is interesting only for
package maintainers, the main purpose of this directory should be to
avoid source tree pollution with scripts and stuff that are useful only
to a few of us.
/tests serve a completely different purpose: it contains tests that are
useful to check acopost integrity on the end-user machine: the data
should be distributed and should be used as a standard step of the
installation procedures.
> /src -- should only keep the source of the distributed programs;
> acopost_test should be moved to /maintain
Probably true. I have not yet understood what is the purpose of
acopost_test, but I think it is probable that it would be useful to make
it part of the test suite as well, so /test/src or even /src would be a
good place for it. We only need to make sure that "make install" does
not install it.
> BRW, I am not completely sure about the name `maintain`, perhaps we
> could go for `devel`.
/devel is a good name for it. But unless we ALL agree to move
maintainance scripts there, I do not think it is a priority to have this
directory as we only have 3 scripts that are candidates to move there
and, as Ulrik reported, autogen.sh usually resides in the top directory
of the source tree.
Bests,
Giulio.
------------------------------------------------------------------------------
Introducing AppDynamics Lite, a free troubleshooting tool for Java/.NET
Get 100% visibility into your production application - at no cost.
Code-level diagnostics for performance bottlenecks with <2% overhead
Download for free and get started troubleshooting in minutes.
http://p.sf.net/sfu/appdyn_d2d_ap1
_______________________________________________
acopost-devel mailing list
acopost-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/acopost-devel
