Would anyone be opposed to a little house cleaning? And yes I'm
volunteering to fix all the relevant build infrastructure and code to
make sure things still work right after the changes. Aside from a
little reorganization, I'd like to migrate our files to a layout that
better matches our install layout. It's less confusing that way.
Here are my initial suggestions:
README.* -> doc/
We're going to get more and more docs, so this is IMO a good idea
since the main dir is already too cluttered.
Docs -> share/data, share/misc, or share/html
This will make our build tree look more like the install tree,
and is a bit clearer to me. Choosing share/data would be
predicated on adopting my ./data/ suggestion below, or we'd have
a conflict.
Gnucash -> share/Gnucash.app-defaults or just Gnucash.app-defaults
This way the name's a lot more indicative of the contents.
Reports -> old/perl-reports
Presuming none of these files are still used. We can move them
here as a precursor to removing them altogether, or they can just
live in old/ indefinitely.
data -> examples or doc/examples
This seems a little clearer to me, but it's not critical. I
would like to think about changing the install destination to
${prefix}/doc/examples, or similar. I tend to think of the
runtime share directory as only for files the program actually
uses.
(Dave, if you're not familiar with moving things around in CVS, I can
help with that. There are two main approaches, and which one you
pick depends on what you want to preserve.)
--
Rob Browning <[EMAIL PROTECTED]> PGP=E80E0D04F521A094 532B97F5D64E3930
--
Gnucash Developer's List
To unsubscribe send empty email to: [EMAIL PROTECTED]
