Re: [Zope-CMF] SVN: CMF.buildout/trunk/src/ Don't use http:// externals for CMF externals.
Hi! Tres Seaver wrote: Log message for revision 110361: Don't use http:// externals for CMF externals. This buildout is for developers: making them do the dance is silly. Changed: _U CMF.buildout/trunk/src/ -=- Property changes on: CMF.buildout/trunk/src ___ Modified: svn:externals - Zope2 http://svn.zope.org/repos/main/Zope/trunk Products.CMFCalendar http://svn.zope.org/repos/main/Products.CMFCalendar/trunk Products.CMFCore http://svn.zope.org/repos/main/Products.CMFCore/trunk Products.CMFDefault http://svn.zope.org/repos/main/Products.CMFDefault/trunk Products.CMFTopic http://svn.zope.org/repos/main/Products.CMFTopic/trunk Products.CMFUid http://svn.zope.org/repos/main/Products.CMFUid/trunk Products.DCWorkflow http://svn.zope.org/repos/main/Products.DCWorkflow/trunk Products.GenericSetup http://svn.zope.org/repos/main/Products.GenericSetup/trunk five.localsitemanager http://svn.zope.org/repos/main/five.localsitemanager/trunk + Zope2 http://svn.zope.org/repos/main/Zope/trunk Products.CMFCalendar svn+ssh://svn.zope.org/repos/main/Products.CMFCalendar/trunk Products.CMFCore svn+ssh://svn.zope.org/repos/main/Products.CMFCore/trunk Products.CMFDefault svn+ssh://svn.zope.org/repos/main/Products.CMFDefault/trunk Products.CMFTopic svn+ssh://svn.zope.org/repos/main/Products.CMFTopic/trunk Products.CMFUid svn+ssh://svn.zope.org/repos/main/Products.CMFUid/trunk Products.DCWorkflow svn+ssh://svn.zope.org/repos/main/Products.DCWorkflow/trunk Products.GenericSetup svn+ssh://svn.zope.org/repos/main/Products.GenericSetup/trunk five.localsitemanager svn+ssh://svn.zope.org/repos/main/five.localsitemanager/trunk I propose to use the new svn:externals format instead. That makes the discussion http:// vs. svn+ssh:// vs. svn:// obsolete because it allows to specify relative externals. IIRC the general policy for the Zope repository is to switch to relative externals after the release of Ubuntu 10.04 LTS, but I guess all people using CMF.buildout have already Subversion =1.5 available. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] SVN: CMF.buildout/trunk/src/ Don't use http:// externals for CMF externals.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/1/10 12:10 , yuppie wrote: IIRC the general policy for the Zope repository is to switch to relative externals after the release of Ubuntu 10.04 LTS, but I guess all people using CMF.buildout have already Subversion =1.5 available. Huh? Since when do we make repository policy based on the release of a particular Linux distribution? Where is this policy described? April fools joke maybe? jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAku0coEACgkQRAx5nvEhZLITsACfQObUJti5M7Kg5AEVUqLg9lI8 YkAAnjPpRYT+yxCS6agouZyUPcR4Al+q =dljU -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] SVN: CMF.buildout/trunk/src/ Don't use http:// externals for CMF externals.
Jens Vagelpohl wrote: On 4/1/10 12:10 , yuppie wrote: IIRC the general policy for the Zope repository is to switch to relative externals after the release of Ubuntu 10.04 LTS, but I guess all people using CMF.buildout have already Subversion=1.5 available. Huh? Since when do we make repository policy based on the release of a particular Linux distribution? Where is this policy described? April fools joke maybe? I might be wrong, but AFAIR this was the last discussion about it on Zope-dev and nobody objected to this mail: https://mail.zope.org/pipermail/zope-dev/2009-September/037693.html Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] SVN: CMF.buildout/trunk/src/ Don't use http:// externals for CMF externals.
Am 01.04.2010, 12:28 Uhr, schrieb yuppie y.2...@wcm-solutions.de: I might be wrong, but AFAIR this was the last discussion about it on Zope-dev and nobody objected to this mail: https://mail.zope.org/pipermail/zope-dev/2009-September/037693.html I think it would be a bit much to extrapolate a policy from that e-mail. Client libraries for developers shouldn't be restricted by the OS - we'd never get anywhere on OS X if that were the case. Anyone on this list who wouldn't be happy with relative URLs for svn:externals? Charlie -- Charlie Clark Helmholtzstr. 20 Düsseldorf D- 40215 Tel: +49-211-938-5360 GSM: +49-178-782-6226 ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] SVN: CMF.buildout/trunk/src/ Don't use http:// externals for CMF externals.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 On 4/1/10 12:28 , yuppie wrote: Jens Vagelpohl wrote: On 4/1/10 12:10 , yuppie wrote: IIRC the general policy for the Zope repository is to switch to relative externals after the release of Ubuntu 10.04 LTS, but I guess all people using CMF.buildout have already Subversion=1.5 available. Huh? Since when do we make repository policy based on the release of a particular Linux distribution? Where is this policy described? April fools joke maybe? I might be wrong, but AFAIR this was the last discussion about it on Zope-dev and nobody objected to this mail: https://mail.zope.org/pipermail/zope-dev/2009-September/037693.html Like Charlie says, you may be overinterpreting that email. There is no such general policy for svn.zope.org. Bringing up that question again certainly doesn't do any harm. I personally have no objections to using relative SVN URLs. jens -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.8 (Darwin) iEYEARECAAYFAku0eWcACgkQRAx5nvEhZLLMngCgo/ZHkiLL+gaGkUD4smhELeTS shIAoI8jkrQAigHGzmTxkMy+HKKb3qVq =ET7G -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] SVN: CMF.buildout/trunk/src/ Don't use http:// externals for CMF externals.
Hi! Jens Vagelpohl wrote: On 4/1/10 12:28 , yuppie wrote: Jens Vagelpohl wrote: On 4/1/10 12:10 , yuppie wrote: IIRC the general policy for the Zope repository is to switch to relative externals after the release of Ubuntu 10.04 LTS, but I guess all people using CMF.buildout have already Subversion=1.5 available. Huh? Since when do we make repository policy based on the release of a particular Linux distribution? Where is this policy described? April fools joke maybe? I might be wrong, but AFAIR this was the last discussion about it on Zope-dev and nobody objected to this mail: https://mail.zope.org/pipermail/zope-dev/2009-September/037693.html Like Charlie says, you may be overinterpreting that email. There is no such general policy for svn.zope.org. Obviously general policy was the wrong term because both of you interpreted it not how I meant it. I agree this decision is not set in stone. Bringing up that question again certainly doesn't do any harm. I personally have no objections to using relative SVN URLs. I don't plan to bring it up again on Zope-dev. I just proposed to make an exception for CMF. Cheers, Yuppie ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] SVN: CMF.buildout/trunk/src/ Don't use http:// externals for CMF externals.
On Thu, Apr 1, 2010 at 1:24 PM, yuppie y.2...@wcm-solutions.de wrote: Jens Vagelpohl wrote: Bringing up that question again certainly doesn't do any harm. I personally have no objections to using relative SVN URLs. I don't plan to bring it up again on Zope-dev. I just proposed to make an exception for CMF. I'm on Subversion 1.6 anyways, so +1 for using the new format for the CMF buildout. Hanno ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] SVN: CMF.buildout/trunk/src/ Don't use http:// externals for CMF externals.
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 yuppie wrote: Hi! Tres Seaver wrote: Log message for revision 110361: Don't use http:// externals for CMF externals. This buildout is for developers: making them do the dance is silly. Changed: _U CMF.buildout/trunk/src/ -=- Property changes on: CMF.buildout/trunk/src ___ Modified: svn:externals - Zope2 http://svn.zope.org/repos/main/Zope/trunk Products.CMFCalendar http://svn.zope.org/repos/main/Products.CMFCalendar/trunk Products.CMFCore http://svn.zope.org/repos/main/Products.CMFCore/trunk Products.CMFDefault http://svn.zope.org/repos/main/Products.CMFDefault/trunk Products.CMFTopic http://svn.zope.org/repos/main/Products.CMFTopic/trunk Products.CMFUid http://svn.zope.org/repos/main/Products.CMFUid/trunk Products.DCWorkflow http://svn.zope.org/repos/main/Products.DCWorkflow/trunk Products.GenericSetup http://svn.zope.org/repos/main/Products.GenericSetup/trunk five.localsitemanager http://svn.zope.org/repos/main/five.localsitemanager/trunk + Zope2 http://svn.zope.org/repos/main/Zope/trunk Products.CMFCalendar svn+ssh://svn.zope.org/repos/main/Products.CMFCalendar/trunk Products.CMFCore svn+ssh://svn.zope.org/repos/main/Products.CMFCore/trunk Products.CMFDefault svn+ssh://svn.zope.org/repos/main/Products.CMFDefault/trunk Products.CMFTopic svn+ssh://svn.zope.org/repos/main/Products.CMFTopic/trunk Products.CMFUid svn+ssh://svn.zope.org/repos/main/Products.CMFUid/trunk Products.DCWorkflow svn+ssh://svn.zope.org/repos/main/Products.DCWorkflow/trunk Products.GenericSetup svn+ssh://svn.zope.org/repos/main/Products.GenericSetup/trunk five.localsitemanager svn+ssh://svn.zope.org/repos/main/five.localsitemanager/trunk I propose to use the new svn:externals format instead. That makes the discussion http:// vs. svn+ssh:// vs. svn:// obsolete because it allows to specify relative externals. IIRC the general policy for the Zope repository is to switch to relative externals after the release of Ubuntu 10.04 LTS, but I guess all people using CMF.buildout have already Subversion =1.5 available. I'm +0 on making this change: I don't konw who will be using this buildout via an anonymous HTTP URL, but if everybody working on CMF is alraedy using SVN = 1.5, I can't see any harm in the 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.9 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iEYEARECAAYFAku0vjAACgkQ+gerLs4ltQ7lkgCff9MMGBc8/ySG+I9v7vwa2xSS W/MAn1/tD/qPq9aysyyADR+K88F8IXGu =99R8 -END PGP SIGNATURE- ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
Re: [Zope-CMF] SVN: CMF.buildout/trunk/src/ Don't use http:// externals for CMF externals.
On Thu, Apr 1, 2010 at 5:39 PM, Tres Seaver tsea...@palladion.com wrote: I'm +0 on making this change: I don't konw who will be using this buildout via an anonymous HTTP URL, but if everybody working on CMF is alraedy using SVN = 1.5, I can't see any harm in the relative externals. I've gone ahead and made the change. One obvious user that doesn't handle svn+ssh urls is the nightly buildbot. So using relative externals seems to be the best option. Hanno ___ Zope-CMF maillist - Zope-CMF@zope.org https://mail.zope.org/mailman/listinfo/zope-cmf See https://bugs.launchpad.net/zope-cmf/ for bug reports and feature requests
