[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: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Tue, 31 Mar 2009 18:54:01 +0200

Lübbe Onken wrote:
> Hi Stefan,
>
> you wrote:
>
>> Lübbe Onken wrote:
>>> Hi Folks,
>>>
>>> I'd like to move things around a bit in the contrib folder. It contains
>>> stuff that is user-relevant and developer-relevant, but not in
>>> consistent locations.
>>>
>>> My Suggestion is to junk the "other" folder (or rename it to "dev") and
>>> have two main folders, either:
>>>
>>> a) "contrib-user" and "contrib-dev" next to each other or
>> I'd prefer this one.
>
> I like Otos suggestion about a "tools" subproject too.
>
>>> b) "contrib" and "contrib/dev" (less renaming and moving around)
>>>
>>> "contrib-user" or just "contrib" as it is now
>>> (This folder should contain only stuff that is interesting for users)
>>> - hook-scripts
>>> - issue-tracker-plugins
>>> - diff-scripts
>> Hmm - the issue tracker plugins are most likely only interesting to
>> developers, not users.
>
> Plugin developers are users of TortoiseSVN too :) What I want to place
> inside contrib-dev is the stuff that only we, the TSVN developers need.
> So a "tools" subproject would serve the same purpose.

Agreed.

>>> "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.
>
> These tools don't just check the docs.

I assume they're also used for the UI translations?
Maybe we should move the 'Languages' folder into the 'docs' folder then?
 Maybe something like this:

/trunk/resources
/trunk/resources/UI (former 'Languages')
/trunk/resources/docs
/trunk/resources/utils (contains the po-checker stuff)

>
>> I'm not sure about the 'drupal-modules', but IMHO it would belong into
>> the www folder.
>
> Isn't the content of the www folder automatically placed on the
> tigris.org web site? I wouldn't want that to happen.

Yes. But what's the difference of having it on the website (with no
links to it) than having it in the repository? It's 'visible' anyway...

>>> Now where shall we put:
>>> other/svnindex (I guess contrib-user)
>> yes.
>>
>>> other/tcvs.reg (no idea)
>>> other/tsvn.reg (no idea)
>> That too belongs in contrib-user.
>>
>>
>>> Suggestions please :)
>>>
>>> Some of the suggested moves/renames surely affect the setup scripts, so
>>> the script wizards should speak up.
>> That's not a big problem. After reorganizing this, the nightly build
>> might be broken for a day or two - no big deal.
>>
>> 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?
>
> The translation status report on our web site runs "svn up" so that it
> always has the latest version of the include and .po files. My idea
> behind using these two externals is that we just have to change the
> external and the translation status report automatically does the right
> thing next time it is run. No need to log into the server.
> Alternatively we could store the branch name inside the script and the
> script checks out a fresh working copy each time it is run.
> But if we come back to Otos suggestion about a "tools" subproject inside
> the repo root, we could place everything there, including the externals.
> I think this is the way to go unless someone comes up with a better idea.

It always depends: a folder in the repo root won't get tagged together
with the trunk. And many tools we use for the build depend on the
version to build.

Stefan

-- 
       ___
  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=1497659
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].

Received on 2009-03-31 18:54:17 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.