[Zope-dev] Zope Tests: 8 OK
Summary of messages to the zope-tests list. Period Tue Sep 8 12:00:00 2009 UTC to Wed Sep 9 12:00:00 2009 UTC. There were 8 messages: 8 from Zope Tests. Tests passed OK --- Subject: OK : Zope-2.10 Python-2.4.6 : Linux From: Zope Tests Date: Tue Sep 8 20:43:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012496.html Subject: OK : Zope-2.11 Python-2.4.6 : Linux From: Zope Tests Date: Tue Sep 8 20:45:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012497.html Subject: OK : Zope-2.12 Python-2.4.6 : Linux From: Zope Tests Date: Tue Sep 8 20:47:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012498.html Subject: OK : Zope-2.12 Python-2.6.2 : Linux From: Zope Tests Date: Tue Sep 8 20:49:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012499.html Subject: OK : Zope-2.12-alltests Python-2.4.6 : Linux From: Zope Tests Date: Tue Sep 8 20:51:55 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012500.html Subject: OK : Zope-2.12-alltests Python-2.6.2 : Linux From: Zope Tests Date: Tue Sep 8 20:53:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012501.html Subject: OK : Zope-trunk Python-2.6.2 : Linux From: Zope Tests Date: Tue Sep 8 20:55:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012502.html Subject: OK : Zope-trunk-alltests Python-2.6.2 : Linux From: Zope Tests Date: Tue Sep 8 20:57:56 EDT 2009 URL: http://mail.zope.org/pipermail/zope-tests/2009-September/012503.html ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] chameleon.core removes the meta http-equiv=content-type tag
Fabio Tranchitella wrote: I hope this is the right mailing list for such a question. Why does chameleon.core removes the meta tag http-equiv=content-type from the output? I have no idea why; I've asked Sidnei to clarify that particular changeset in Chameleon (although I suspect it was just carried over as-is from ``zope.pagetemplate``). \malthe ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] status of ZTK KGS?
Hi there, What's the status of the ZTK KGS? Is the stuff still on Jim's branch? svn+ssh://svn.zope.org/repos/main/zopetoolkit/branches/jim-kgs/kgs What's the plan for merging this branch? Is documentation about it all being written to add to the Zope Toolkit documentation? http://docs.zope.org/zopetoolkit/ Will it contain an easy link to a buildbot overview page with some explanation on how to interpret its results? What can be done to make progress? Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Subversion externals versus mirroring
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, a long-standing issue with our mirror of svn.zope.org are the absolute URLs of externals: they require the repository to be available on a given URL. I propose to use relative URLs for externals. I guess a complete update isn't necessary, but I'd like to improve the situation and start using them from now on. Maybe we should also put a commit hook in place as a safety belt? However, this requires Subversion 1.5 which we are using on the server already, but I don't know whether we assume clients are 1.5 or higher. As a side effect this will also make svn/svn+ssh work in a nicer way (IMHO) as the externals will follow the protocol of what you used for checkout. Christian - -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqnoB8ACgkQdUt9X/gknwI9lgCcDjO320EGllkcaJT8rA7aR+pa rVIAn2Qh5D7sIGMmNPSyClx72PHBhL80 =5696 -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] zope.location.pickling.PathPersistent and BBB
While wondering about the ITraverser interface being defined by zope.location, we noticed that the zope.location.pickling.PathPersistent class (which is this package's only user of the interface) is decorated with a recent BBB comment, and had been questioned by a XXX comment for some time before that. The class doesn't seem to be used anywhere in Zope, so removing it would rid zope.location of some unused code as well as make it possible to move ITraverser back to zope.traversing where it fits much better conceptionally. What are your opinions on this, does anyone object? -- Thomas ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
On Wed, Sep 9, 2009 at 8:31 AM, Christian Theunec...@gocept.com wrote: As a side effect this will also make svn/svn+ssh work in a nicer way (IMHO) as the externals will follow the protocol of what you used for checkout. I like that externals to svn:... are read-only, though I don't know offhand whether we have a policy about this. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
Hi there, Christian Theune wrote: a long-standing issue with our mirror of svn.zope.org are the absolute URLs of externals: they require the repository to be available on a given URL. I propose to use relative URLs for externals. I guess a complete update isn't necessary, but I'd like to improve the situation and start using them from now on. Maybe we should also put a commit hook in place as a safety belt? However, this requires Subversion 1.5 which we are using on the server already, but I don't know whether we assume clients are 1.5 or higher. I certainly still use a SVN 1.4.x client, being on Ubuntu 8.04 LTS (released just last year). I don't think SVN 1.5 is common enough yet to make such a move possible. As a side effect this will also make svn/svn+ssh work in a nicer way (IMHO) as the externals will follow the protocol of what you used for checkout. That's definitely cool; keeps tripping me up when I want to check into an external. Usually I use externals when I'm developing multiple things at once... So, I don't think it's time yet, but I do support this on the longer term. We could record a decision to do this at least for the ZTK in the ZTK decisions document. What about mid-next year for requiring Subversion 1.5.x? There's nothing against us deciding things well ahead of time! A ZTK timeline planning document, anyone? (Ubuntu should've released a new LTS by then too. :) Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
Martijn Faassen schrieb: Hi there, Christian Theune wrote: a long-standing issue with our mirror of svn.zope.org are the absolute URLs of externals: they require the repository to be available on a given URL. I propose to use relative URLs for externals. I guess a complete update isn't necessary, but I'd like to improve the situation and start using them from now on. Maybe we should also put a commit hook in place as a safety belt? However, this requires Subversion 1.5 which we are using on the server already, but I don't know whether we assume clients are 1.5 or higher. I certainly still use a SVN 1.4.x client, being on Ubuntu 8.04 LTS (released just last year). I don't think SVN 1.5 is common enough yet to make such a move possible. you still can use 1.4 clients an a 1.5 server I think.. robert ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Move implementation of getParent to zope.location?
Hi there, On 08/12/2009 12:06 PM, Jim Fulton wrote: Right. I understood this in the original proposal. Given that it doesn't break the existing API, I have no major problem with it, which is why I didn't bother to respond in the first place. I have a small problem that it fattens an existing API. As far as I understand, the method is there and used and should have been in that existing API in the first place. Also, as you say it's only a small problem for you, I guess Thomas can go ahead moving it. I have a larger problem that we are wasting time on this. The cleanup doesn't seem worth it to me. I especially don't like that *I'm* spending time on this rather than, say, working on the kgs or our buildout discussions. I see truth in what you say, but this answer also takes energy from people who'd like to spend time on improving small things (which quickly sum up to larger things) pushing them away from contributing. I don't think we can afford that. Christian -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
On Wed, Sep 9, 2009 at 2:40 PM, Martijn Faassenfaas...@startifact.com wrote: Christian Theune wrote: However, this requires Subversion 1.5 which we are using on the server already, but I don't know whether we assume clients are 1.5 or higher. I certainly still use a SVN 1.4.x client, being on Ubuntu 8.04 LTS (released just last year). I don't think SVN 1.5 is common enough yet to make such a move possible. We moved all the Plone repositories (including the rather massively used collective) to Subversion 1.5.6 a while ago. So far there have been no complaints by anyone. And as Robert noted you can use a Subversion 1.4 client with a 1.5 server just fine. I think doing the server upgrade very soon (tm) shouldn't be a problem. Using relative externals or proper merge history might be something that shouldn't be required yet, though. Maybe people should be free and allowed to do this for any package not being part of the ZTK right away. That might introduce some incentive for those still using age-old Subversion clients ;) Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
On Wed, Sep 9, 2009 at 8:31 AM, Christian Theunec...@gocept.com wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, a long-standing issue with our mirror of svn.zope.org are the absolute URLs of externals: they require the repository to be available on a given URL. I propose to use relative URLs for externals. I guess a complete update isn't necessary, but I'd like to improve the situation and start using them from now on. Maybe we should also put a commit hook in place as a safety belt? However, this requires Subversion 1.5 which we are using on the server already, but I don't know whether we assume clients are 1.5 or higher. As a side effect this will also make svn/svn+ssh work in a nicer way (IMHO) as the externals will follow the protocol of what you used for checkout. Sounds good to me. Jim -- Jim Fulton ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
Hanno Schlichting wrote: On Wed, Sep 9, 2009 at 2:40 PM, Martijn Faassenfaas...@startifact.com wrote: Christian Theune wrote: However, this requires Subversion 1.5 which we are using on the server already, but I don't know whether we assume clients are 1.5 or higher. I certainly still use a SVN 1.4.x client, being on Ubuntu 8.04 LTS (released just last year). I don't think SVN 1.5 is common enough yet to make such a move possible. We moved all the Plone repositories (including the rather massively used collective) to Subversion 1.5.6 a while ago. So far there have been no complaints by anyone. And as Robert noted you can use a Subversion 1.4 client with a 1.5 server just fine. I think doing the server upgrade very soon (tm) shouldn't be a problem. Ah, I perhaps misunderstood. I figured the resolving of relative externals would be a problem with a Subversion 1.4.x client. Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
On Sep 9, 2009, at 15:30 , Martijn Faassen wrote: Ah, I perhaps misunderstood. I figured the resolving of relative externals would be a problem with a Subversion 1.4.x client. There's two different issues being confused here. SVN 1.4 clients will work with SVN 1.5 repositories in general. However, that's not the real issue here. The issue is the new-style externals definitions that allow you to use relative paths. Those relative paths will not work for SVN 1.4 clients. jens smime.p7s Description: S/MIME cryptographic signature ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
On Wed, Sep 9, 2009 at 10:35 AM, Jens Vagelpohlj...@dataflake.org wrote: SVN 1.4 clients will work with SVN 1.5 repositories in general. However, that's not the real issue here. The issue is the new-style externals definitions that allow you to use relative paths. Those relative paths will not work for SVN 1.4 clients. Is that based on an assumption or someone tried and verified that it doesnt work? -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] chameleon.core removes the meta http-equiv=content-type tag
On Wed, Sep 9, 2009 at 9:13 AM, Malthe Borchmbo...@gmail.com wrote: Fabio Tranchitella wrote: I hope this is the right mailing list for such a question. Why does chameleon.core removes the meta tag http-equiv=content-type from the output? I have no idea why; I've asked Sidnei to clarify that particular changeset in Chameleon (although I suspect it was just carried over as-is from ``zope.pagetemplate``). As far as I remember, it was just carried over as-is. Some (local) tests that expected it to be gone were failing with chameleon. -- Sidnei ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
On Sep 9, 2009, at 15:59 , Sidnei da Silva wrote: On Wed, Sep 9, 2009 at 10:35 AM, Jens Vagelpohlj...@dataflake.org wrote: SVN 1.4 clients will work with SVN 1.5 repositories in general. However, that's not the real issue here. The issue is the new-style externals definitions that allow you to use relative paths. Those relative paths will not work for SVN 1.4 clients. Is that based on an assumption or someone tried and verified that it doesnt work? It doesn't. I tried. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] chameleon.core removes the meta http-equiv=content-type tag
The meta http-equiv=content-type content=... is used to identify the encoding of the file providing the template. This has nothing to do with the encoding of the output resource, which is determined by the application. In the case of the Zope publisher, Unicode output from the template is converted to UTF-8 by default, and the charset is set appropriately for text/* content types. This gets to the basic problem that templates have both input and output concerns, and there's currently no clean way to separate the two without additional syntax or metadata support. There's no one way to handle this; zope.pagetemplate.pagetemplatefile contains specific choices which made sense at the time; I think these are still reasonable choices. Existing applications may well require the current behavior, so it's unreasonable to change that, regardless of how attractive a new set of choices may appear. The right way to make new choices is to create a new class that embodies those choices, or which allows runtime configuration, and use that as appropriate. -Fred -- Fred L. Drake, Jr.fdrake at gmail.com Chaos is the score upon which reality is written. --Henry Miller ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
Jens Vagelpohl wrote: On Sep 9, 2009, at 15:30 , Martijn Faassen wrote: Ah, I perhaps misunderstood. I figured the resolving of relative externals would be a problem with a Subversion 1.4.x client. There's two different issues being confused here. SVN 1.4 clients will work with SVN 1.5 repositories in general. However, that's not the real issue here. The issue is the new-style externals definitions that allow you to use relative paths. Those relative paths will not work for SVN 1.4 clients. Okay, no objection to upgrading the server to 1.5 now. But requiring 1.5 as clients will need some more discussion. I take it there are two main reasons to do so: * relative URLs in externals * better merge tracking Regards, Martijn ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
On 2009-9-9 14:54, Hanno Schlichting wrote: On Wed, Sep 9, 2009 at 2:40 PM, Martijn Faassenfaas...@startifact.com wrote: Christian Theune wrote: However, this requires Subversion 1.5 which we are using on the server already, but I don't know whether we assume clients are 1.5 or higher. I certainly still use a SVN 1.4.x client, being on Ubuntu 8.04 LTS (released just last year). I don't think SVN 1.5 is common enough yet to make such a move possible. We moved all the Plone repositories (including the rather massively used collective) to Subversion 1.5.6 a while ago. So far there have been no complaints by anyone. And as Robert noted you can use a Subversion 1.4 client with a 1.5 server just fine. I think doing the server upgrade very soon (tm) shouldn't be a problem. Relative externals are handled on the svn client, not the svn server. Wichert. -- Wichert Akkerman wich...@wiggy.net It is simple to make things. http://www.wiggy.net/ It is hard to make things simple. ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
On Sep 9, 2009, at 17:05 , Martijn Faassen wrote: Jens Vagelpohl wrote: SVN 1.4 clients will work with SVN 1.5 repositories in general. However, that's not the real issue here. The issue is the new-style externals definitions that allow you to use relative paths. Those relative paths will not work for SVN 1.4 clients. Okay, no objection to upgrading the server to 1.5 now. It's been 1.5 for a while now, so that can be excluded from any further discussion. This is a client-only problem. jens ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
On 09/09/2009 05:05 PM, Martijn Faassen wrote: Jens Vagelpohl wrote: On Sep 9, 2009, at 15:30 , Martijn Faassen wrote: Ah, I perhaps misunderstood. I figured the resolving of relative externals would be a problem with a Subversion 1.4.x client. There's two different issues being confused here. SVN 1.4 clients will work with SVN 1.5 repositories in general. However, that's not the real issue here. The issue is the new-style externals definitions that allow you to use relative paths. Those relative paths will not work for SVN 1.4 clients. Okay, no objection to upgrading the server to 1.5 now. That has been done a good while ago already (I was probably ambiguous in my mail). But requiring 1.5 as clients will need some more discussion. I take it there are two main reasons to do so: * relative URLs in externals * better merge tracking For some interpretation of better. -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
On Wed, Sep 9, 2009 at 6:40 PM, Christian Theunec...@gocept.com wrote: On 09/09/2009 05:05 PM, Martijn Faassen wrote: Okay, no objection to upgrading the server to 1.5 now. That has been done a good while ago already (I was probably ambiguous in my mail). Damn, Jens is just doing too much of an awesome job and not talking about it ;) But requiring 1.5 as clients will need some more discussion. I take it there are two main reasons to do so: * relative URLs in externals * better merge tracking For some interpretation of better. better as in merge tracking exists now vs. there was nothing so far. I wouldn't call the merge tracking great in any way, but it is better than the previous state of having nothing at all. But then again most of Zope doesn't have many active branches, except for Zope2 and CMF maybe. Most packages only have a maintained trunk, so this isn't so relevant. Hanno ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
On Wed, Sep 9, 2009 at 12:40 PM, Christian Theunec...@gocept.com wrote: On 09/09/2009 05:05 PM, Martijn Faassen wrote: * better merge tracking For some interpretation of better. My team tried pretty hard to use 1.5's merge tracking and we could never get it to work well for us. The only advantage we ended up seeing was that we could freshen a branch from a trunk easily. Even that didn't buy us much because we previously had been using the relatively easy approach of rebranching from the trunkand merging from the stale branch to the new, fresh branch. The limitation of only being able to merge a feature branch back to the trunk once was also quite irritating. Plus the merge info properties constantly polluted svn diff and svn stat output as well as our commit email (the latter is fixable of course). After trying for a few months we abandoned it. YMMV. -- Benji York Senior Software Engineer Zope Corporation ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
What about upgrading server to 1.6. Subversion 1.6 has many new features. From http://subversion.tigris.org/svn_1.6_releasenotes.html : * Improved handling of authentication data * Repository root relative URLs * Improvements to svn:externals * Detection of tree conflicts * Filesystem storage improvements * Ctypes Python Bindings * Improved interactive conflict resolution * Sparse directory exclusion * Logging support for svnserve * New public HTTP URI syntax for examining history * Command-line client improvements * API changes, improvements, and much language bindings work * More than 65 new bug fixes, enhancements Regards, Baiju M ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 robert rottermann wrote: Martijn Faassen schrieb: Hi there, Christian Theune wrote: a long-standing issue with our mirror of svn.zope.org are the absolute URLs of externals: they require the repository to be available on a given URL. I propose to use relative URLs for externals. I guess a complete update isn't necessary, but I'd like to improve the situation and start using them from now on. Maybe we should also put a commit hook in place as a safety belt? However, this requires Subversion 1.5 which we are using on the server already, but I don't know whether we assume clients are 1.5 or higher. I certainly still use a SVN 1.4.x client, being on Ubuntu 8.04 LTS (released just last year). I don't think SVN 1.5 is common enough yet to make such a move possible. you still can use 1.4 clients an a 1.5 server I think.. I don't think such clients will be able to grok newer features (such as the proposed relative externals). Tres. - -- === Tres Seaver +1 540-429-0999 tsea...@palladion.com Palladion Software Excellence by Designhttp://palladion.com -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFKqAW/+gerLs4ltQ4RAqIgAKCHb+AVt3KDo4A+G5Qr0UXo5I0ErACgo1S0 nW8cF+T1Wq2AwkX8GG3Vjz0= =ubsl -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
Re: [Zope-dev] Subversion externals versus mirroring
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 09/09/2009 07:12 PM, Benji York wrote: On Wed, Sep 9, 2009 at 12:40 PM, Christian Theunec...@gocept.com wrote: On 09/09/2009 05:05 PM, Martijn Faassen wrote: * better merge tracking For some interpretation of better. My team tried pretty hard to use 1.5's merge tracking and we could never get it to work well for us. The only advantage we ended up seeing was that we could freshen a branch from a trunk easily. Even that didn't buy us much because we previously had been using the relatively easy approach of rebranching from the trunkand merging from the stale branch to the new, fresh branch. The limitation of only being able to merge a feature branch back to the trunk once was also quite irritating. Plus the merge info properties constantly polluted svn diff and svn stat output as well as our commit email (the latter is fixable of course). After trying for a few months we abandoned it. YMMV. Same here. We also ended up in many deadlock situations having to sacrifice chickens for SVN to resume operations. That's why we started investigating alternatives which are better at branching and merging. Christian - -- Christian Theune · c...@gocept.com gocept gmbh co. kg · forsterstraße 29 · 06112 halle (saale) · germany http://gocept.com · tel +49 345 1229889 0 · fax +49 345 1229889 1 Zope and Plone consulting and development -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/ iEYEARECAAYFAkqok5YACgkQdUt9X/gknwLr+QCdHHnFGExGT3E3FFgVmKqow78g y6AAn3ent24aED7DzH8gdN+XDMdJ/tLQ =Zhv/ -END PGP SIGNATURE- ___ Zope-Dev maillist - Zope-Dev@zope.org https://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - https://mail.zope.org/mailman/listinfo/zope-announce https://mail.zope.org/mailman/listinfo/zope )
