Time to retire trunk
John Simons
Can we delete the trunk?
Is this going to affect the git migration?
Does anyone see any problems?
I know that there are a few projects still hanging from the trunk, eg samples, ..., what do we do with these?
Cheers
John
Win 1 of 4 Sony home entertainment packs thanks to Yahoo!7. Enter now.
Mauricio Scheffer
http://groups.google.com/group/horn-development/browse_thread/thread/270d86c674152b04
It seems that in order to build the whole trunk, Horn needs to
implement this: http://code.google.com/p/hornget/issues/detail?id=10
About git: I'm putting the history in the "super project" (what in svn
is now the trunk): http://github.com/mausch/castle instead of the
individual projects (e.g. http://github.com/mausch/Castle.Services.Transaction
). So no trunk would mean duplicating the history in each of the
projects.
Cheers,
Mauricio
On Dec 9, 2:39 pm, John Simons <johnsimons...@yahoo.com.au> wrote:
> With all the projects now building and referencing compiled dependencies, I think it is time to make a judgement call on the future of the trunk in svn.
>
> Can we delete the trunk?
> Is this going to affect the git migration?
> Does anyone see any problems?
>
> I know that there are a few projects still hanging from the trunk, eg samples, ..., what do we do with these?
>
> Cheers
> John
>
G. Richard Bellamy
from svn, yes?
Sent from my mobile device. Please excuse any errors or omissions.
On Dec 9, 2009, at 10:47 AM, Mauricio Scheffer <mauricio...@gmail.com
>
> You received this message because you are subscribed to the Google
> Groups "Castle Project Development List" group.
> To post to this group, send email to castle-pro...@googlegroups.com
> .
> To unsubscribe from this group, send email to castle-project-d...@googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en
> .
>
>
Daniel Hölbling
Mauricio Scheffer
24 projects => 1.87 GB => *very* slow to clone the whole thing.
On Dec 9, 4:33 pm, Daniel Hölbling <hoelblin...@gmail.com> wrote:
> How much history volume are we talking here per repo if we duplicate?
>
> On Wed, Dec 9, 2009 at 7:58 PM, G. Richard Bellamy
>
>
> > We could keep the superproject in git for history, even after deleting
> > from svn, yes?
>
> > Sent from my mobile device. Please excuse any errors or omissions.
>
>
> > > I asked about this some time ago on the horn group:
>
> > > It seems that in order to build the whole trunk, Horn needs to
> > > implement this:http://code.google.com/p/hornget/issues/detail?id=10
>
> > > About git: I'm putting the history in the "super project" (what in svn
> > > For more options, visit this group at
> >http://groups.google.com/group/castle-project-devel?hl=en
> > > .
>
> > --
>
> > You received this message because you are subscribed to the Google Groups
> > "Castle Project Development List" group.
> > To post to this group, send email to castle-pro...@googlegroups.com
> > .
> > To unsubscribe from this group, send email to
Mauricio Scheffer
git superproject either. It's the same concept really.
On Dec 9, 3:58 pm, "G. Richard Bellamy" <rbell...@pteradigm.com>
wrote:
> from svn, yes?
>
> Sent from my mobile device. Please excuse any errors or omissions.
>
>
>
> > wrote:
> > I asked about this some time ago on the horn group:
> > It seems that in order to build the whole trunk, Horn needs to
> > implement this:http://code.google.com/p/hornget/issues/detail?id=10
>
> > About git: I'm putting the history in the "super project" (what in svn
G. Richard Bellamy
discussed this in the context of sub-modules, and decided against it,
IIRC. It seems to me that we're trying to manage two conflicting
concerns:
1. Making git conform to the old structure in order to maintain the
history,
2. Separating the projects to loosen the coupling of dependencies.
So, why not create each project in it's own repo, with the appropriate
set of history for that project? The buildscripts would be a sub-
module of each project (as would a buildtools, if we go on that
direction). This seems to me to adhere more closely with our
intentions WRT the separation of projects...
Am I missing something?
-rb
Sent from my mobile device. Please excuse any errors or omissions.
Daniel Hölbling
To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.
Markus Zywitza
> http://groups.google.com/group/horn-development/browse_thread/thread/270d86c674152b04
as dependencies?
-Markus
Markus Zywitza
> from svn, yes?
But I would retire the TC builds of the trunk.
-Markus
Mauricio Scheffer
"Horn at the minute needs to reference a code repository and needs to
have a
build_with instruction in order to work.
We could certainly build something that referenced all the castle
subprojects but we still need something at the top of the tree to
build. "
On Dec 9, 5:42 pm, Markus Zywitza <markus.zywi...@gmail.com> wrote:
> 2009/12/9 Mauricio Scheffer <mauricioschef...@gmail.com>:
> > I asked about this some time ago on the horn group:
Markus Zywitza
> subprojects but we still need something at the top of the tree to
> build. "
-Markus
Mauricio Scheffer
http://github.com/mausch/castle has all the history
Each project (e.g. http://github.com/mausch/Castle.MonoRail ) only has
recent history that goes back to the split from the svn trunk (around
8/24/2009)
> > > > > .
> > > > > For more options, visit this group at
> > > >http://groups.google.com/group/castle-project-devel?hl=en
> > > > > .
>
> > > > --
>
> > > > You received this message because you are subscribed to the Google
> > Groups
> > > > "Castle Project Development List" group.
> > > > To post to this group, send email to
> > castle-pro...@googlegroups.com
> > > > .
> > > > To unsubscribe from this group, send email to
Mauricio Scheffer
you want to build the whole thing (I wonder if we still want this) you
end up with the history being repeated 24 times (once per project) so
the total clone time gets unbearable.
I'll try to sum up the whole situation in a single message, maybe
start a wiki page.
--
Mauricio
On Dec 9, 5:16 pm, "G. Richard Bellamy" <rbell...@pteradigm.com>
wrote:
> discussed this in the context of sub-modules, and decided against it,
> IIRC. It seems to me that we're trying to manage two conflicting
> concerns:
> 1. Making git conform to the old structure in order to maintain the
> history,
> 2. Separating the projects to loosen the coupling of dependencies.
>
> So, why not create each project in it's own repo, with the appropriate
> set of history for that project? The buildscripts would be a sub-
> module of each project (as would a buildtools, if we go on that
> direction). This seems to me to adhere more closely with our
> intentions WRT the separation of projects...
>
> Am I missing something?
>
> -rb
>
> Sent from my mobile device. Please excuse any errors or omissions.
>
>
>
> > wrote:
> > IIRC it would be about 80MB per project.
> > 24 projects => 1.87 GB => *very* slow to clone the whole thing.
>
> > On Dec 9, 4:33 pm, Daniel Hölbling <hoelblin...@gmail.com> wrote:
> >> How much history volume are we talking here per repo if we duplicate?
>
> >> On Wed, Dec 9, 2009 at 7:58 PM, G. Richard Bellamy
> >> <rbell...@pteradigm.com>wrote:
>
> >>> We could keep the superproject in git for history, even after
> >>> deleting
> >>> from svn, yes?
>
> >>> Sent from my mobile device. Please excuse any errors or omissions.
>
> >>> On Dec 9, 2009, at 10:47 AM, Mauricio Scheffer
> >>> <mauricioschef...@gmail.com
> >>> > wrote:
>
> >>>> I asked about this some time ago on the horn group:
>
> >>>http://groups.google.com/group/horn-development/browse_thread/thread/
> >>> ...
>
> >>>> It seems that in order to build the whole trunk, Horn needs to
> >>>> implement this:http://code.google.com/p/hornget/issues/detail?id=10
>
> >>>> About git: I'm putting the history in the "super project" (what
> >>>> in svn
Henry Conceição
project with a single command.
Cheers,
Henry Conceição
John Simons
The only issue is as Mauricio pointed out this:http://code.google.com/
p/hornget/issues/detail?id=10
But I think we can fix that by using a little batch file :)
However there could be issues with compatibility between all the
projects as we are experiencing right now:
http://groups.google.com/group/castle-project-devel/browse_thread/thread/18837752b50af5d
Cheers
John
On Dec 10, 10:09 am, Henry Conceição <henry.concei...@gmail.com>
wrote:
> project with a single command.
>
> Cheers,
> Henry Conceição
>
> On Wed, Dec 9, 2009 at 8:51 PM, Mauricio Scheffer
>
John Simons
we can retire it.
/trunk/docs <- Do we need this? Can it be deleted?
/trunk/Experiments/* <- There are a few project here, I think the most
important is AnakiaNet, so I'm thinking of moving it to be a top level
project, any objections?
<- In regards to the rest, is there
anything else worth keeping?
/trunk/Facilities/* <- A few facilities here, I think most if not all
have already been moved to Windsor/Microkernel, can this be deleted?
/trunk/Samples/* <- Richard, what do you want to do with these? Move
to be a top level project?
<- Also, if we move these the site build
script will break! Need to update that.
/trunk/Setup <- Don't know what to do with this, my first though is
delete it because is so old (VS2003), thoughts?
/trunk/SharedLibs <- I think we can safely delete these, am I right?
/trunk/Tools/VSNetWizards <- Same has Setup delete it because is too
old (VS2003).
Markus Zywitza
-Markus
2009/12/12 John Simons <johnsi...@yahoo.com.au>:
John Simons
On Dec 12, 9:07 pm, Markus Zywitza <markus.zywi...@gmail.com> wrote:
> /trunk/docs has the HTML needed for generation of the API docs.
>
> -Markus
>
John Simons
/trunk/Experiments/AnakiaNet moved to /AnakiaNet
/trunk/docs moved to /site/apidocs
/trunk/Samples moved to /Samples
We still have:
/trunk/Experiments/* <- do we need this now that AnakiaNet has been
moved?
/trunk/Facilities/* <- A few facilities here, I think most if not all
have already been moved to Windsor/Microkernel, can this be deleted?
/trunk/Setup <- Don't know what to do with this, my first though is
delete it because is so old (VS2003), thoughts?
/trunk/SharedLibs <- I think we can safely delete these, anyone
opposed?
/trunk/Tools/VSNetWizards <- Same has Setup delete it because is too
old (VS2003).
Cheers
John
John Simons
Krzysztof, has moved Remoting, EventWiring and TypedFactory tests out
of /trunk/Facilities/.
So this means that /trunk/Facilities/* should be ok to be deleted.
Cheers
John
John Simons
Otherwise we keep on getting these:
http://groups.google.com/group/castle-project-users/t/b6726a8e14725636
Cheers
John
On Dec 23 2009, 11:50 am, John Simons <johnsimons...@yahoo.com.au>
wrote:
> > > There are still a few thing in thetrunkthat need to be moved, before
Jonathon Rossi
--
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
--
Jono
John Simons
On Jan 13, 2:10 pm, Jonathon Rossi <j...@jonorossi.com> wrote:
> Since it is no longer building and we have migrated to standalone projects
> it does seem like the way to go. However, I think we need to make an
> official release of all the projects so we do have a base line.
>
> > castle-project-d...@googlegroups.com<castle-project-devel%2Bunsu...@googlegroups.com>
John Simons
Roelof Blom
Jonathon Rossi
Roelof Blom
Krzysztof Koźmic
It's very easy to provide link to
Krzysztof Koźmic
Please review the following list of dependencies, and fill in missing
informatin if there's any.
I'm especially interested why AR integration has dependency in NVelicity...
According to NDepend, here are non-BCL assemblies
Castle.MonoRail.Framework uses:
- Castle.Core - Released
- Castle.Components.Binder - Released
- Castle.Components.Validator - Released
- Castle.Components.Pagination - Released
- Newtonsoft.Json - 3rd party
- Castle.Components.Common.EmailSender - integrated to Core - released
- Castle.Components.DictionaryAdapter - Released
Looks like we're all good here.
In addition to that:
===View engines
==Castle.MonoRail.WindsorExtension:
- Castle.MicroKernel - Released
- Castle.Windsor - Released
- Castle.DynamicProxy2 - Released
==Castle.MonoRail.Views.Brail:
- Boo.Lang.Compiler - 3rd party
- Boo.Lang.Extensions - 3rd party
- anrControls.Markdown.NET - 3rd party
- Boo.Lang - 3rd party
- Boo.Lang.Parser - 3rd party
==Castle.MonoRail.Views.AspView: (no additional dependencies)
==Castle.MonoRail.Framework.Views.NVelocity: (shouldn't it be renamed to
- Castle.MonoRail.Views.NVelocity for consistency?)
- NVelocity - this is out fork?
===We also have:
==Castle.MonoRail.TransformFilters (no additional dependencies
==Castle.MonoRail.TestSupport
- Cassini - 3rd party
==Castle.MonoRail.ActiveRecordSupport
- Castle.ActiveRecord - Released (or soon to be)
- NHibernate - 3rd party
- Castle.Components.Common.TemplateEngine - internal Castle dependency
- Castle.Components.Common.TemplateEngine.NVelocityTemplateEngine -
This is strange. Is it intentional?
==Castle.Components.Common.TemplateEngine.NVelocityTemplateEngine: (no
additional dependencies)
==Castle.Components.Common.TemplateEngine: (no additional dependencies)
John Simons
Richard.
Castle.MonoRail.ActiveRecordSupport has a dependency on a view engine
because it uses it internally for scaffolding and NVelocity is the
only view engine that is supported by AR scaffolding -
http://www.castleproject.org/monorail/documentation/trunk/integration/arscaffold.html
Yes, I agree it doesn;t make sense, but that is the way it is right
now!
Cheers
John
On Jan 14, 4:21 am, Krzysztof Koźmic <krzysztof.koz...@gmail.com>
wrote:
Krzysztof Koźmic
That expliains a lot.
Richard, how is it going with your releases? Do you need a hand?
Krzysztof
On 2010-01-13 21:41, John Simons wrote:
> Actually we still waiting on v1.1.1 for Validation and Binder from
> Richard.
>
> Castle.MonoRail.ActiveRecordSupport has a dependency on a view engine
> because it uses it internally for scaffolding and NVelocity is the
> only view engine that is supported by AR scaffolding -
> http://www.castleproject.org/monorail/documentation/trunk/integration/arscaffold.html
> Yes, I agree it doesn;t make sense, but that is the way it is right
> now!
>
> Cheers
> John
>
>
> On Jan 14, 4:21 am, Krzysztof Ko�mic<krzysztof.koz...@gmail.com>
John Simons
The one click link would be for the latest trunk successful build of a
project right?
And it would d/l the zip file eg. castle-arintegration-facility-
net-3.5-release-24.zip ?
And we would put this links in http://www.castleproject.org/castle/projects.html
or http://www.castleproject.org/subversion.html ?
Cheers
John
On Jan 14, 3:53 am, Krzysztof Koźmic <krzysztof.koz...@gmail.com>
wrote:
> Yes, I very much agree.
>
> It's very easy to provide link to
> On 2010-01-13 11:43, Roelof Blom wrote:
>
> > Yeah.
>
> > I am not very much at home in TC, but it looks like we could use the
> > Artifact dependencies to do this.
>
> > -- Roelof.
>
> > On Wed, Jan 13, 2010 at 11:35 AM, Jonathon Rossi <j...@jonorossi.com
> > <mailto:j...@jonorossi.com>> wrote:
>
> > I think everyone agrees. I know Krzysztof really does.
>
> > On Wed, Jan 13, 2010 at 8:33 PM, Roelof Blom
> > <roelof.b...@gmail.com <mailto:roelof.b...@gmail.com>> wrote:
>
> > We also should provide a one-click download of *all* projects.
> > It's ultra cumbersome to click through TC to get everything
> > you want.
>
> > On Wed, Jan 13, 2010 at 4:10 AM, Jonathon Rossi
> > <j...@jonorossi.com <mailto:j...@jonorossi.com>> wrote:
>
> > Since it is no longer building and we have migrated to
> > standalone projects it does seem like the way to go.
> > However, I think we need to make an official release of
> > all the projects so we do have a base line.
>
> > On Wed, Jan 13, 2010 at 11:57 AM, John Simons
> > <johnsimons...@yahoo.com.au
> > <mailto:johnsimons...@yahoo.com.au>> wrote:
>
> > Can we please get a decision on retiring the trunk?
>
> > Otherwise we keep on getting these:
> > http://groups.google.com/group/castle-project-users/t/b6726a8e14725636
>
> > Cheers
> > John
>
> > On Dec 23 2009, 11:50 am, John Simons
> > <johnsimons...@yahoo.com.au
> > <mailto:johnsimons...@yahoo.com.au>>
> > wrote:
> > > Another update
> > > Krzysztof, has moved Remoting, EventWiring and
> > TypedFactory tests out
> > > of /trunk/Facilities/.
>
> > > So this means that /trunk/Facilities/* should be ok
> > to be deleted.
>
> > > Cheers
> > > John
>
> > > On Dec 20, 4:31 pm, John Simons
> > <johnsimons...@yahoo.com.au
> > <mailto:castle-pro...@googlegroups.com>.
> > To unsubscribe from this group, send email to
> > castle-project-d...@googlegroups.com
> > <mailto:castle-project-devel%2Bunsu...@googlegroups.com>.
> > For more options, visit this group at
> > http://groups.google.com/group/castle-project-devel?hl=en.
>
> > --
> > Jono
>
> > --
> > You received this message because you are subscribed to
> > the Google Groups "Castle Project Development List" group.
> > To post to this group, send email to
> > castle-pro...@googlegroups.com
> > <mailto:castle-pro...@googlegroups.com>.
> > To unsubscribe from this group, send email to
> > castle-project-d...@googlegroups.com
> > <mailto:castle-project-devel%2Bunsu...@googlegroups.com>.
> > For more options, visit this group at
> > http://groups.google.com/group/castle-project-devel?hl=en.
>
> > --
> > You received this message because you are subscribed to the
> > Google Groups "Castle Project Development List" group.
> > To post to this group, send email to
> > castle-pro...@googlegroups.com
> > <mailto:castle-pro...@googlegroups.com>.
> > To unsubscribe from this group, send email to
> > castle-project-d...@googlegroups.com
> > <mailto:castle-project-devel%2Bunsu...@googlegroups.com>.
> > For more options, visit this group at
> > http://groups.google.com/group/castle-project-devel?hl=en.
>
> > --
> > Jono
>
> > --
> > You received this message because you are subscribed to the Google
> > Groups "Castle Project Development List" group.
> > To post to this group, send email to
> > castle-pro...@googlegroups.com
> > <mailto:castle-pro...@googlegroups.com>.
> > To unsubscribe from this group, send email to
> > castle-project-d...@googlegroups.com
> > <mailto:castle-project-devel%2Bunsu...@googlegroups.com>.
G. Richard Bellamy
Ken Egozi
--
You received this message because you are subscribed to the Google Groups "Castle Project Development List" group.
To post to this group, send email to castle-pro...@googlegroups.com.
To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/castle-project-devel?hl=en.
--
Ken Egozi.
http://www.kenegozi.com/blog
http://www.delver.com
http://www.musicglue.com
http://www.castleproject.org
http://www.idcc.co.il - הכנס הקהילתי הראשון למפתחי דוטנט - בואו בהמוניכם
Roelof Blom
Roelof Blom
John Simons
You can find them here - http://www.castleproject.org/community/releaseguide.html
Cheers
John
From: Ken Egozi <ego...@gmail.com>
To: castle-pro...@googlegroups.com
Sent: Thu, 14 January, 2010 9:02:41 AM
Subject: Re: Monorail release
John Simons
> > I guess there would also be demand for a one-click download of *all* projects in *one* zip.
All projects in one zip, why?
Don't u just pick what u need?
On Jan 14, 9:14 am, Roelof Blom <roelof.b...@gmail.com> wrote:
> Maybe we should put this on UV.
>
> 2010/1/13 Roelof Blom <roelof.b...@gmail.com>
>
> > I guess there would also be demand for a one-click download of *all*
> > projects in *one* zip.
>
> > -- Roelof.
>
> > 2010/1/13 John Simons <johnsimons...@yahoo.com.au>
> >> > > castle-project-d...@googlegroups.com<castle-project-devel%2Bunsu...@googlegroups.com>
> >> > > <mailto:
> >> castle-project-devel%2Bunsu...@googlegroups.com<castle-project-devel%252Buns...@googlegroups.com>
> >> >.
> >> > > For more options, visit this group at
>
> >>http://groups.google.com/group/castle-project-devel?hl=en.
>
> >> > > --
> >> > > Jono
>
> >> > > --
> >> > > You received this message because you are subscribed to
> >> > > the Google Groups "Castle Project Development List" group.
> >> > > To post to this group, send email to
> >> > > castle-pro...@googlegroups.com
> >> > > <mailto:castle-pro...@googlegroups.com>.
> >> > > To unsubscribe from this group, send email to
> >> > > castle-project-d...@googlegroups.com<castle-project-devel%2Bunsu...@googlegroups.com>
> >> > > <mailto:
> >> castle-project-devel%2Bunsu...@googlegroups.com<castle-project-devel%252Buns...@googlegroups.com>
> >> >.
> >> > > For more options, visit this group at
> >> > > http://groups.google.com/group/castle-project-devel?hl=en.
>
> >> > > --
> >> > > You received this message because you are subscribed to the
> >> > > Google Groups "Castle Project Development List" group.
> >> > > To post to this group, send email to
> >> > > castle-pro...@googlegroups.com
> >> > > <mailto:castle-pro...@googlegroups.com>.
> >> > > To unsubscribe from this group, send email to
> >> > > castle-project-d...@googlegroups.com<castle-project-devel%2Bunsu...@googlegroups.com>
> >> > > <mailto:castle-project-devel%2Bunsu...@googlegroups.com<castle-project-devel%252Buns...@googlegroups.com>
> >> >.
> >> > > For more options, visit this group at
> >> > > http://groups.google.com/group/castle-project-devel?hl=en.
>
> >> > > --
> >> > > Jono
>
> >> > > --
> >> > > You received this message because you are subscribed to the Google
> >> > > Groups "Castle Project Development List" group.
> >> > > To post to this group, send email to
> >> > > castle-pro...@googlegroups.com
> >> > > <mailto:castle-pro...@googlegroups.com>.
> >> > > To unsubscribe from this group, send email to
> >> > > castle-project-d...@googlegroups.com<castle-project-devel%2Bunsu...@googlegroups.com>
> >> > > <mailto:castle-project-devel%2Bunsu...@googlegroups.com<castle-project-devel%252Buns...@googlegroups.com>
> >> >.
> >> > > For more options, visit this group at
> >> > > http://groups.google.com/group/castle-project-devel?hl=en.
>
> >> > > --
> >> > > You received this message because you are subscribed to the Google
> >> > > Groups "Castle Project Development List" group.
> >> > > To post to this group, send email to
> >> > > castle-pro...@googlegroups.com.
> >> > > To unsubscribe from this group, send email to
>
> ...
>
> read more >>
Henry Conceição
Cheers,
Henry Conceição
2010/1/13 John Simons <johnsi...@yahoo.com.au>:
> To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.
G. Richard Bellamy
-----Original Message-----
From: castle-pro...@googlegroups.com
[mailto:castle-pro...@googlegroups.com] On Behalf Of John Simons
Sent: Wednesday, January 13, 2010 2:56 PM
To: Castle Project Development List
UV ?
ubsc...@googlegroups.com>
> >> > > <mailto:
> >> castle-project-devel%2Bunsu...@googlegroups.com<castle-project-
> >> devel%252Buns...@googlegroups.com>
> >> >.
> >> > > For more options, visit this group at
>
> >>http://groups.google.com/group/castle-project-devel?hl=en.
>
> >> > > --
> >> > > Jono
>
> >> > > --
> >> > > You received this message because you are subscribed to
> >> > > the Google Groups "Castle Project Development List"
group.
> >> > > To post to this group, send email to
> >> > > castle-pro...@googlegroups.com
> >> > > <mailto:castle-pro...@googlegroups.com>.
> >> > > To unsubscribe from this group, send email to
> >> > >
castle-project-d...@googlegroups.com<castle-project-devel%2Buns
ubsc...@googlegroups.com>
> >> > > <mailto:
> >> castle-project-devel%2Bunsu...@googlegroups.com<castle-project-
> >> devel%252Buns...@googlegroups.com>
> >> >.
> >> > > For more options, visit this group at
> >> > >
http://groups.google.com/group/castle-project-devel?hl=en.
>
> >> > > --
> >> > > You received this message because you are subscribed to the
> >> > > Google Groups "Castle Project Development List" group.
> >> > > To post to this group, send email to
> >> > > castle-pro...@googlegroups.com
> >> > > <mailto:castle-pro...@googlegroups.com>.
> >> > > To unsubscribe from this group, send email to
> >> > >
castle-project-d...@googlegroups.com<castle-project-devel%2Buns
ubsc...@googlegroups.com>
> >> > >
> >> > > <mailto:castle-project-devel%2Bunsu...@googlegroups.com<cas
> >> > > tle-project-devel%252Buns...@googlegroups.com>
> >> >.
> >> > > For more options, visit this group at
> >> > > http://groups.google.com/group/castle-project-devel?hl=en.
>
> >> > > --
> >> > > Jono
>
> >> > > --
> >> > > You received this message because you are subscribed to the
Google
> >> > > Groups "Castle Project Development List" group.
> >> > > To post to this group, send email to
> >> > > castle-pro...@googlegroups.com
> >> > > <mailto:castle-pro...@googlegroups.com>.
> >> > > To unsubscribe from this group, send email to
> >> > >
castle-project-d...@googlegroups.com<castle-project-devel%2Buns
ubsc...@googlegroups.com>
> >> > >
> >> > > <mailto:castle-project-devel%2Bunsu...@googlegroups.com<cas
Roelof Blom
To unsubscribe from this group, send email to castle-project-d...@googlegroups.com.
Markus Zywitza
> I guess there would also be demand for a one-click download of *all*
> projects in *one* zip.
Can't we create a Horn package descriptor for this?
-Markus
Roelof Blom
Markus Zywitza
Krzysztof Koźmic
Ayende?