Edward Pilatowicz wrote:
On Thu, Oct 29, 2009 at 07:51:52AM -0700, Garrett D'Amore wrote:
Sebastien Roy wrote:
On Thu, 2009-10-29 at 07:17 -0700, Garrett D'Amore wrote:
Sebastien Roy wrote:
On Thu, 2009-10-29 at 06:54 -0700, Garrett D'Amore wrote:
Edward Shu wrote:
+1. I would like the package for the "community supported
hardware" will be self contained. That is,
ON tree is not necessary to build the package.
It would be nice, but we'll need the ON headers at least, I think.
Logistically speaking, to make this work at all, I would think that your
repository would need to be a child of a snapshot of the ON gate. This
very much seems to me to be a project (rather than a consolidation) that
perpetually synchronizes with ON by regularly pulling and merging from
some snapshot of the ON gate (just like any other ON-based project).
Copying a collection of header files from the ON gate seems like a poor
man's way of simply doing development in a snapshot of ON itself.
I don't think a child will be as easy to work with, if only because
I'll constantly be doing merges.
you could make your cshw repository was a sub repository that lived
within an ON clone. ie, it could live in an ON clone under usr/cshw/.
that way you could leverage all the ON build infrastructure, proto area
for building against, etc, without ever having to deal with hg merges.
just a thought.
Thats sort of what I had in mind, but I wasn't going to make it a
subdirectory, but a side by side deal. I don't *want* to use the ON
build infrastructure, because frankly its clumsy and problematic, and if
I'm starting from scratch I can do something *far* simpler that works
more easily and resolves some of the annoying problems (the ability to
build both x86 and sparc in the same workspace for example).
-- Garrett
ed
_______________________________________________
driver-discuss mailing list
driver-disc...@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/driver-discuss
_______________________________________________
opensolaris-code mailing list
opensolaris-code@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/opensolaris-code
