2013/5/30 Giulio Paci
> If it is documentation and example, the right installation path should
> be /usr/share/doc/acopost/examples/.
> I also think those two files should be distributed with the source.
>
>
Ok, I am convinced. Those are, after all, examples, and it is up to the
user to just cop
On 30/05/2013 17:50, Tiago Tresoldi wrote:
> 2013/5/30 Giulio Paci mailto:giuliop...@gmail.com>>
>
> > I had suggested putting everything in /data just to reduce the
> number of
> > directories and to be consistent (/bin with binary files, /src with
> > source files, /data with use
2013/5/30 Giulio Paci
> > I had suggested putting everything in /data just to reduce the number of
> > directories and to be consistent (/bin with binary files, /src with
> > source files, /data with user-experience files, etc.)
> >
> > But sub-modules for the actual language models, such the ava
Hello,
On 5/30/13 5:36 PM, Giulio Paci wrote:
>
> I agree to keep the scripts in the top directory.
>
> Summarizing I think that we basically agreed on these points:
> 1) moving /bin to /src/scripts
> 2) moving /example to /data
> 3) leave everything else as it is
> 4) eventually create /devel or
On 30/05/2013 15:22, Ulrik Sandborg-Petersen wrote:
>> /maintain -- development&debug scripts, C testing, etc.
>> /maintain/data -- data for testing, fake language corpus and
>> eventually its pre-trained models, etc.
>
> Why not call it /test and simply have tests in there? That way, the
> purpo
On 30/05/2013 17:03, Tiago Tresoldi wrote:
> 2013/5/30 Giulio Paci mailto:giuliop...@gmail.com>>
>
> >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
2013/5/30 Giulio Paci
> >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.
>
Moving them to /src/scripts would make se
>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 Giu
Hello to you both,
I answer inline below.
On 05/30/2013 02:31 PM, Tiago Tresoldi wrote:
In reply to both Ulrik and Giulio
> a) autogen.sh is traditionally placed in the root directory. I have
> seen it in lots of packages, and always in the root of the sources.
I agree, but it used
In reply to both Ulrik and Giulio
> a) autogen.sh is traditionally placed in the root directory. I have
> > seen it in lots of packages, and always in the root of the sources.
>
> I agree, but it used to be harder in the past to recreate autoconf files
> than just "autoreconf --install".
>
I th
Il 30/05/2013 08:55, Ulrik Sandborg-Petersen ha scritto:
>> 1) why not moving autogen.sh, rmfiles.sh and valgrind.sh in a maintainance/
>> directory?
>
> I would actually advocate keeping them in the root directory for the
> following reasons:
>
> a) autogen.sh is traditionally placed in the ro
11 matches
Mail list logo
