[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Restructuring the contrib folder

From: Oto BREZINA <otik_at_e-posta.sk>
Date: Mon, 30 Mar 2009 22:45:01 +0200

>> "contrib-dev" or "contrib/dev", a sub-folder of contrib
>> (This folder should contain only stuff that is used by the TortoiseSVN
>> dev team)
>> - drupal-modules
>> - po-checker
>> - translation-status
>>
>
> I don't think we should name that folder 'contrib' because it doesn't
> contain user contributions.
>
> I suggest to move the 'translation-status' and 'po-checker' inside our
> doc folder somewhere.
>
> I'm not sure about the 'drupal-modules', but IMHO it would belong into
> the www folder.
>
>
I would preffer move all this tools outside of source and even trunk.
This tools are - from my point of view - separate project and don't
share history with main project. I may be wrong in it, or it may break
some "project organization style". - Just suggestion.
> If we're reorganizing stuff anyway: I really don't like the externals in
> drupal-modules/translation-status. I know you need them for the scripts
> which run on the server. But they already *are* in our sourcetree and
> the externals duplicate them.
> Would it be possible to change either the scripts to use the original
> files or change the update script on the server to get them from the
> original location? Or if that's not suitable, create a new folder in the
> repo root where those externals are set and then use that folder instead
> on the server?
>
I fill same. In current layout po-checker should have its own externals
... (and it worse case it makes loop).
> Stefan
>
Oto

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=1485928

To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-03-31 07:05:06 CEST

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.