On 12/1/2010 2:20 PM, Stenehall wrote:
I know this have been discussed before but nothing have really
happend. Moving scripts/ and 3rdparty/ into system/ would make it
simpler to manage in a couple of different ways.
1. Manual updates would be simpler, just replace system/, no need for
multiple folders to keep track of.
2. It would make it simpler to use externals in svn, one single
checkout to manage.
3. It would also make it possible to keep system/ in a seperate repo
on github for people to use as a submodule. Removing the need for
multiple branches and rebases.
So, in short, I'd like to reopen the debate about moving scripts and
3rdparty/ into system/. Who's for it? Anyone against it?
3rdparty is a core plugin and theme include directory. If you put those
directories in there, Habari is able to find them just as if they were
in /user.
The intent of this was at least in part to facilitate packaging of
specific-purpose profiles for distribution.
/scripts does not have this functionality.
No, I have no idea why the scripts that are currently in the core
/3rdparty are still in there. There really isn't a reason for plain
Habari to ship with an included /3rdparty directory other than
potentially as a placeholder - a sketchy reason at best.
As for /scripts, it could go inside /system, but then there's no simple
or obvious place to put non-system scripts. I guess that's kind of the
case anyway, if you have to overwrite the /scripts directory on upgrades.
Owen
--
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at http://groups.google.com/group/habari-dev
