opensync-devel

[Opensync-devel] New repository layout

[Armin B. <arm...@de...>]

Hi,

we are planning to move the plugins out of the opensync dir. What should
the new layout be?

branches/
trunk/ (opensync)
tags/
plugins/

or

opensync/branches/
opensync/trunk/
opensync/tags
syncml-plugin/
kdepim-plugin/ etc

or something else? What do you think?

Armin

Re: [Opensync-devel] New repository layout

[Pierre O. <drz...@dr...>]

Armin Bauer wrote:
> Hi,
> 
> we are planning to move the plugins out of the opensync dir. What should
> the new layout be?
> 
> branches/
> trunk/ (opensync)
> tags/
> plugins/
> 
> or
> 
> opensync/branches/
> opensync/trunk/
> opensync/tags
> syncml-plugin/
> kdepim-plugin/ etc
> 
> or something else? What do you think?
> 
> Armin

Since each plugin has its own build structure they should be in seperate
directories in one form or another. But it might be cleaner to have them
under a plugins directory first. I.e:

opensync/branches/
opensync/trunk/
opensync/tags
plugins/syncml-plugin/
plugins/kdepim-plugin/ etc

The only big requirement I have is one 'configure' per tarball since it
makes rpm-building a bit more sane =)

Rgds
Pierre

Re: [Opensync-devel] New repository layout

[Eduardo P. H. <eha...@co...>]

On Tue, Mar 22, 2005 at 02:06:37PM +0100, Pierre Ossman wrote:
<snip>
>=20
> Since each plugin has its own build structure they should be in seperate
> directories in one form or another. But it might be cleaner to have them
> under a plugins directory first. I.e:
>=20
> opensync/branches/
> opensync/trunk/
> opensync/tags
> plugins/syncml-plugin/
> plugins/kdepim-plugin/ etc

Good point. Prepend "plugins/" to all plugin directories on the layouts
shown on my previous message. I think we don't need the "-plugin" suffix
if we are inside a "plugins/" directory, too.


--=20
Eduardo

Re: [Opensync-devel] New repository layout

[Eduardo P. H. <eha...@co...>]

On Tue, Mar 22, 2005 at 01:37:29PM +0100, Armin Bauer wrote:
> Hi,

Hi,

>=20
> we are planning to move the plugins out of the opensync dir. What should
> the new layout be?
>=20
> branches/
> trunk/ (opensync)
> tags/
> plugins/
>=20
> or
>=20
> opensync/branches/
> opensync/trunk/
> opensync/tags
> syncml-plugin/
> kdepim-plugin/ etc

My preferred layout has the problem of moving opensync to a new
subdirectory. It would be:

trunk/opensync/
trunk/sync-plugin/
trunk/kdepim-plugin/

But I agree with any layout, as long as they stay in a single repository
(i.e. allow cheap moves and copies between, without losing the history).

My order of preference is:

trunk/opensync/
trunk/sync-plugin/
trunk/kdepim-plugin/
branches/
tags/
(I like this because it doesn't break the trunk/branches/tags convention.
But it would move opensync to a subdirectory)

opensync/branches/
opensync/trunk/
opensync/tags
syncml-plugin/
kdepim-plugin/ etc
(I like this for the same reason as above. Altought it "breaks" the
trunk/branches/ tags convention on the first directory level, it keeps it
on the second directory level)
(I agree with this layout if, and only if, they stay on a single repository)


branches/
trunk/ (opensync)
tags/
plugins/
(This layout "breaks" the branches/trunk/tags convention, but I think it
can be justified if we don't want to move "opensync" to a subdirectory,
and if the layout above would imply on not having a single repository)

>=20
> or something else? What do you think?
>=20
> Armin



--=20
Eduardo