----- Original Message -----
From: "Kristis Makris" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Cc: <[email protected]>
Sent: Thursday, December 07, 2006 7:39 PM
Subject: Re: label_name ...
On Thu, 2006-12-07 at 14:04 +0100, [EMAIL PROTECTED] wrote:
Hi Kristis
I have been tuning the installation form some time and I have 2
questions:
- the feature around label_name - is there any specific reason that
scmbuga
assumes the directory must be in root - ie. /branch /tags, not
/project_name/branch & /project_name/tags
If scmbug assumes, somewhere, the directory must be in root, it's
probably a limitation of some original design; and should be lifted. It
seems that SCM_Functions.pm.in:get_label_date suffers from this (used by
the VDD Generator). Have you found other places ?
We should fix this, yes.
OK - but it can be fixed in config files - All you have to do is to play
with regex:
label_directories => [
'tags',
'branches'
],
ex. you just need to add -all tags in the second level
'[^/]*/tags
The pros is that you have the complete control of where you are looking for
so there is no constraints to for examples 'tags' subdirectores deep within
the project.
You need also to change naming rules - for ex.
'^.+?_RELEASE_[0-9]+-[0-9]+-[0-9]+$',
to:
'^.*?_?RELEASE_[0-9]+-[0-9]+-[0-9]+$',
as there is no need to name build within the directory.
Therefore we need to change default config templates only....
http://bugzilla.mkgnu.net/show_bug.cgi?id=893
For example, we should require the user to supply in both the VDD
Generator and the Merger a label name like "project_name/tags/sometag"
instead of just "sometag". So while you are implementing the Merger,
assume the bigger label name, and I'll take care of fixing the VDD
generator.
How does this sound ?
OK - how about proposed solution in config file? Looks fine for me...
- what do you think of declining any updates in tags by scmbug?
That's a great idea. It was recommended in the past:
http://bugzilla.mkgnu.net/show_bug.cgi?id=859#c4
When 859 is implemented you would be able to somehow mark tags as
"closed/frozen" branches in which new commits would be disallowed.
It proposes a stricter control I thought - the problem I see is that we
would duplicate some of the functionality of 'auth' file within subversion.
Don't you think? Do we have an infrastructure to analyze this file from
scmbug?
I reckoned to implement only something like this in the configuration :
frozen_directories => [
'tags'
],
+ small changes in perl scripts
_______________________________________________
scmbug-users mailing list
[email protected]
http://lists.mkgnu.net/cgi-bin/mailman/listinfo/scmbug-users
