Mark Banner wrote:
On 27/07/2009 17:25, Rich Megginson wrote:
1) checkout just the c-sdk
hg clone http://hg.mozilla.org/whatever/it/is
Ftr, (afaict,)
'whatever/it' is the (optional) path under which the 'is' repository lives.
'clone' clones a (full) repository: that's why I wrote that a separate
('c-sdk' only) repository was wanted.
3) tag individual and separate c-sdk releases
hg tag -r <changeset> MY_TAG
Likewise, 'tag' tags a revision, which means it applies to the whole
repo. (branch).
4) produce individual source code releases of the c-sdk
You can:
hg clone ....
hg update -r MY_TAG
Then you could zip it up, which would include the history, or I expect
we could probably copy one of the source tar ball commands from the
mozilla-central/comm-central build systems that would get you just the
source files.
While I understand zipping the source files in the c-sdk dir of a
working copy,
I don't quite follow your steps :-(
The only thing I can think of with having them all-in-one is that one
tag would tag all the files in the repository, but I guess that isn't
really an issue.
(see above)
From a comm-central view point I think we could cope with either,
although if we did an all-in-one I'd probably think about moving the
xpcom sdk back to the LDAP repository as that would also help building
binary extensions against xulrunner with LDAP.
I don't know much about the xpcom sdk,
but, in the "one repo per sdk", this sdk could just move to its own repo
too...
_______________________________________________
dev-tech-ldap mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-tech-ldap
