Just checked out r2951

My initial directory structure now looks like this

[email protected] [~/www/habari]# ls
./  ../  .svn/  LICENSE  docs/  htdocs/  tests/
[email protected] [~/www/habari]# ls htdocs
./   .htaccess  3rdparty/  NOTICE  index.php  system/
../  .svn/      LICENCE    doc/    scripts/   user/

So I can no longer install Habari by visiting

http://mysite/habari

On Dec 15, 12:42 pm, "Chris Meller" <[email protected]> wrote:
> On Sat, Dec 13, 2008 at 11:05 PM, rick c <[email protected]> wrote:
>
> > I'm all for getting everything out of root that is possible. Looking
> > at the ASL 2.0 license,http://www.apache.org/licenses/LICENSE-2.0, I
> > can't see anything that would require the license and notice files to
> > be in the root, so I don't see why they couldn't be placed in the /
> > docs directory. Others, of course, my see something different or feel
> > we are better served with them being in their current location.
>
> > As the originator of the ticket in question regarding placing the
> > config file in /user by default, I see it as a good move that should
> > ease upgrades, since it's one less thing to watch out for when
> > upgrading. It should also make backing up one's site easier, as well
> > as allow one to move one's blog more easily, since you can just grab
> > the /user directory and run with it. Having to manually move the
> > config file once during this update is worth the future benefits.
>
> > Rick
>
> Just wanted to point out what I said in IRC the other night. According 
> tohttp://www.apache.org/dev/apply-license.html#newyou MUST include LICENSE
> and NOTICE in the root, and you SHOULD include a comment with the
> abbreviated license in each file.
>
> So those two have to stay...
--~--~---------~--~----~------------~-------~--~----~
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
-~----------~----~----~----~------~----~------~--~---

Reply via email to