Horn descriptors
1 view
Skip to first unread message
Mauricio Scheffer
Dec 15, 2009, 9:39:11 AM12/15/09
to Castle Project Development List
Paul Cowan and I have been working on the Castle descriptors for Horn.
There are now individual descriptors for each project, like:
Monorail: http://hornget.net/packages/web/castle.monorail/castle.monorail-trunk
ActiveRecord: http://hornget.net/packages/ioc/castle.activerecord/castle.activerecord-trunk
etc
It needs a couple of minor adjustments (e.g. Spring being included in
ActiveRecord) but it should work. Please check it out.
Now a couple of questions about this:
* Other than building things like Monorail +
Facilities.ActiveRecordIntegration, what value would have a descriptor
that builds all Castle projects?
* Should we use fixed versions for our dependencies? Since Horn
builds do not run any tests (they could, but then they would take
*forever*) things can break very easily. (even worse than
http://groups.google.com/group/castle-project-devel/browse_thread/thread/18837752b50af5d
since we'd use external projects' trunks)
* On git migration: I added shallow clones to horn, so what I
described in http://groups.google.com/group/castle-project-devel/msg/1fe66437349e8e46
would no longer be a problem. If everyone agrees, I'll duplicate the
history in each project. It will make the transition easier and this
way we don't need the git superproject (trunk) anymore.
Comments and questions welcome.
--
Mauricio
There are now individual descriptors for each project, like:
Monorail: http://hornget.net/packages/web/castle.monorail/castle.monorail-trunk
ActiveRecord: http://hornget.net/packages/ioc/castle.activerecord/castle.activerecord-trunk
etc
It needs a couple of minor adjustments (e.g. Spring being included in
ActiveRecord) but it should work. Please check it out.
Now a couple of questions about this:
* Other than building things like Monorail +
Facilities.ActiveRecordIntegration, what value would have a descriptor
that builds all Castle projects?
* Should we use fixed versions for our dependencies? Since Horn
builds do not run any tests (they could, but then they would take
*forever*) things can break very easily. (even worse than
http://groups.google.com/group/castle-project-devel/browse_thread/thread/18837752b50af5d
since we'd use external projects' trunks)
* On git migration: I added shallow clones to horn, so what I
described in http://groups.google.com/group/castle-project-devel/msg/1fe66437349e8e46
would no longer be a problem. If everyone agrees, I'll duplicate the
history in each project. It will make the transition easier and this
way we don't need the git superproject (trunk) anymore.
Comments and questions welcome.
--
Mauricio
John Simons
Dec 15, 2009, 5:19:40 PM12/15/09
to Castle Project Development List
That's awesome news :)
Who maintains the project descriptors? Should we maintain them and
host them in our svn?
Reply to your questions inline
On Dec 16, 1:39 am, Mauricio Scheffer <mauricioschef...@gmail.com>
wrote:
>
> * Should we use fixed versions for our dependencies?
Yes I think we should because we are now using binary dependencies and
that is the version of the dependency we support.
Since Horn
> builds do not run any tests (they could, but then they would take
> *forever*) things can break very easily. (even worse thanhttp://groups.google.com/group/castle-project-devel/browse_thread/thr...
Who maintains the project descriptors? Should we maintain them and
host them in our svn?
Reply to your questions inline
On Dec 16, 1:39 am, Mauricio Scheffer <mauricioschef...@gmail.com>
wrote:
> Paul Cowan and I have been working on the Castle descriptors for Horn.
> There are now individual descriptors for each project, like:
>
> Monorail:http://hornget.net/packages/web/castle.monorail/castle.monorail-trunk
> ActiveRecord:http://hornget.net/packages/ioc/castle.activerecord/castle.activereco...
> There are now individual descriptors for each project, like:
>
> Monorail:http://hornget.net/packages/web/castle.monorail/castle.monorail-trunk
> etc
>
> It needs a couple of minor adjustments (e.g. Spring being included in
> ActiveRecord) but it should work. Please check it out.
>
> Now a couple of questions about this:
>
> * Other than building things like Monorail +
> Facilities.ActiveRecordIntegration, what value would have a descriptor
> that builds all Castle projects?
I myself do not see value in this, what everyone else thinks?
>
> It needs a couple of minor adjustments (e.g. Spring being included in
> ActiveRecord) but it should work. Please check it out.
>
> Now a couple of questions about this:
>
> * Other than building things like Monorail +
> Facilities.ActiveRecordIntegration, what value would have a descriptor
> that builds all Castle projects?
>
> * Should we use fixed versions for our dependencies?
that is the version of the dependency we support.
Since Horn
> builds do not run any tests (they could, but then they would take
> since we'd use external projects' trunks)
>
> * On git migration: I added shallow clones to horn, so what I
> described inhttp://groups.google.com/group/castle-project-devel/msg/1fe66437349e8e46
>
> * On git migration: I added shallow clones to horn, so what I
Mauricio Scheffer
Dec 15, 2009, 9:35:34 PM12/15/09
to Castle Project Development List
Descriptors live in this github repo: http://github.com/dagda1/hornget
In fact, horn is currently hardcoded to fetch descriptors from this
repo only.
Paul is the maintainer of this repo, but of course anyone can fork and
make changes.
About the stability of the builds, I'm +1 too for using fixed
versions, but I'll ask on the Horn groups.
--
Mauricio
In fact, horn is currently hardcoded to fetch descriptors from this
repo only.
Paul is the maintainer of this repo, but of course anyone can fork and
make changes.
About the stability of the builds, I'm +1 too for using fixed
versions, but I'll ask on the Horn groups.
--
Mauricio
John Simons
Dec 16, 2009, 1:05:06 AM12/16/09
to Castle Project Development List
These are probably discussions for the horn mailing list but...
In my opinion the descriptors to build a project should live with the
project, not on the horn repository.
And it should be the project leader/developers responsibility to
maintain their own horn descriptors.
I know that horn can get the latest from all my project dependencies
(that's what is all about), but as a developer I would like to be able
to nominate what versions of dependencies to use to compile my
project, even the trunk version, because of compatibility issues as we
are seeing in Castle trunk right now.
Cheers
John
On Dec 16, 1:35 pm, Mauricio Scheffer <mauricioschef...@gmail.com>
wrote:
In my opinion the descriptors to build a project should live with the
project, not on the horn repository.
And it should be the project leader/developers responsibility to
maintain their own horn descriptors.
I know that horn can get the latest from all my project dependencies
(that's what is all about), but as a developer I would like to be able
to nominate what versions of dependencies to use to compile my
project, even the trunk version, because of compatibility issues as we
are seeing in Castle trunk right now.
Cheers
John
On Dec 16, 1:35 pm, Mauricio Scheffer <mauricioschef...@gmail.com>
wrote:
Mauricio Scheffer
Dec 16, 2009, 11:08:15 AM12/16/09
to Castle Project Development List
Jump into the discussion: http://groups.google.com/group/horn-development/browse_thread/thread/ab4a3ba003b85e6a
Reply all
Reply to author
Forward
0 new messages