Re: pear svntag - Tag naming
| From: | Helgi Þormar Þorbjörnsson | Date: | Wed, 29 Jul 2009 09:33:41 +0000 |
| Subject: | Re: pear svntag - Tag naming | ||
| References: | 1 2 3 4 | Groups: | php.pear.dev |
| Request: | Send a blank email to pear-dev+get-52518@lists.php.net to get a copy of this message | ||
On Wed, Jul 29, 2009 at 10:21 AM, Greg Beaver<greg@chiaraquartet.net> wrote:
> David Jean Louis wrote:
>> Helgi Þormar Þorbjörnsson a écrit :
>>>
>>> A compromise would be do have it simply as 0.2.0 and skip
>>> $packagename- and release-
>>>
>>> I would be interested in hearing what other people think about this
>>> before a PEAR release is done.
>>>
>>> - Helgi
>>>
>>
>> I'd suggest:
>>
>> tags/releases/X.Y.Z
>>
>> Tags are not necessarily releases, granted, they are *most* the time but
>> I'd like to keep an option to tag the code for a non release.
>>
>> And with the release-X.Y.Z naming scheme we may end up with a mess of
>> names in the tags/ directory in that case.
>
> Hi,
>
> I agree with Christian, subpackages should be supported.
>
> I don't think pear svntag is really necessary since it's now a 1-liner.
> All we need is a well-documented standard.
Well, I have written it already - It's even more code than cvstag due
to the remove tag / slide tag features :)
I dare you to do this by hand btw, given that it's not just a svn cp
trunk -> tags ;-)
You need to copy all files that are in the package.xml so it ends up
being more than a one liner, and this feature is essential for those
sub package guys.
> how about:
> either tags/releases/X.Y.Z or tags/releases/Pname/X.Y.Z for those rare
> packages with subpackages.
Well I guess I could also check if it's a sub package and then use
pname, if it's not a sub package I'd put it directly in the releases.
Shouldn't be much hassle.
- Helgi