Newbie : how to setup my repository-ies

David M. Carr david at carrclan.us
Wed Nov 7 16:31:14 UTC 2012


On Wed, Nov 7, 2012 at 8:52 AM, RAPPAZ Francois
<francois.rappaz at unifr.ch> wrote:
> My lib folder contains external jar files, yes, but since my projects are rather small, depending on one or two external libraries, I have always succeed with having genjar grabing the needed class files in my jar.
>
> David M. Carr wrote:
>>If it contains other projects, I recommend creating a new folder
>>structure, copying in just the portions that you want to post to
>>Google Code, and testing that it builds.  You'd then initialize the
>>Mercurial repository in the root of this new folder structure.
>
> That's what I've done. I was wondering how to connect the portion I copied with the whole source tree. Creating a second repository in src for all my source files did not work, since I got a message saying the repository were disconnected.
>
> What about cloning the whole src repository and then removing the source file I don't use for the application1 ? what will happen if I merge the changes done in application1 back to src ? will mercurial delete the files ?
>
>
> François
> _______________________________________________
> Mercurial mailing list
> Mercurial at selenic.com
> http://selenic.com/mailman/listinfo/mercurial

If the portion that you copied from "the whole source tree" into the
project that you're posting is small and/or unlikely to change often,
I'd consider either not worrying about keeping it "connected" (that
is, instead allowing it to evolve independently) or manually
synchronizing as needed (using file copies or file editing instead of
Mercurial operations).

If the portion is larger, frequently modified, or important to stay in
synch, I'd recommend trying to come up one or more "components" that
make sense to publish from that portion.  Each component would be its
own repository, with its own independent build.  The project you're
publishing would then depend on the JARs for these components in a
similar way to how it depends on external dependencies (and the same
sort of approaches to acquiring JARs, such as Ivy, can be used).

-- 
David M. Carr
david at carrclan.us



More information about the Mercurial mailing list