keryx team mailing list archive

[Chris Oliver <excid3@xxxxxxxxx>]

high-level-directory is referring to how back in 0.91 the packages
were downloaded into the win32/packages folder if you used the Windows
version, and linux/packages if you used that for anything. This one is
implemented, you are right.

per-project-packages is for the packages directory to be split up into
smaller folders containing the packages for each project separately
(which might lead to duplicates) so we weren't sure if this would be a
good idea to add but I think this will be a non-default option that
users can set in 1.0.

That make sense?

On 7/30/09, Uno Zwei <watch.and.learn@xxxxxxxxxxx> wrote:
>
> Hello Keryx Development Team, now I know where the actual yakking happens.
>
> In the blueprints for keryx, I see two similar pieces:
> 'high-level-directory' and 'per-project-packages'. Are these actually the
> same, if so then 'high-level-directory' has been Implemented.
>
> _________________________________________________________________
> Stay in the loop and chat with friends, right from your inbox!
> http://go.microsoft.com/?linkid=9671354


-- 
Chris Oliver
http://excid3.com