monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] nvm.source-tree-cleanup


From: Stephen Leake
Subject: Re: [Monotone-devel] nvm.source-tree-cleanup
Date: Thu, 03 Feb 2011 07:43:25 -0500
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/23.2 (windows-nt)

Stephen Leake <address@hidden> writes:

> The non-source files for building the win32 installer are modpath.iss,
> monotone.bmp, and monotone.iss.in. There is also related code in
> Makefile.am.
>
> ...
>
> I'm not strongly opposed to moving those three files to
> <root>/win32_install (do you have a suggested name?), but I don't see
> the "consistency" argument. 

Perhaps the argument is "files in <root>/src/... are source for the
executable, not anything else". Similarly, "files in <root>/doc are
source for the documentation". That makes sense.

Then we could have "files in <root>/packages/... are source for
distribution packages and/or installers (except Makfile.am goes where
the autotools need it)". Then we could have:

    <root>/packages/mingw/   3 win32 installer files 
    <root>/packages/cygwin/  1 cygport file
    <root>/packages/visualc/ renamed from <root>/visualc
    <root>/packages/mac/     renamed from <root>/mac
    <root>/packages/debian/  debian stuff
    ...

I'm not clear if visualc and mac are "packages" (and thus similar to
*.iss), or "build tools" (and thus similar to Makefile.am). Either way,
I suggest they belong in <root>/packages.

Perhaps <root>/distros instead of <root>/packages.

It might be good to add some of the rationale for the directory tree to
HACKING. But I guess it's pretty clear (I did figure it out with only a
little thought :).

-- 
-- Stephe



reply via email to

[Prev in Thread] Current Thread [Next in Thread]