Mailing List Archive: Zope: CMF

GenericSetup 1.4 release

Index | Next | Previous | View Threaded

wichert at wiggy

Mar 2, 2008, 2:15 PM

Post #1 of 18 (847 views)
Permalink

GenericSetup 1.4 release

The improvements GenericSetup 1.4/trunk has over the 1.3 series are a
big part of Plone 3.1. With that moving towards it first alpha release
this Friday it would be practical if there was a GenericSetup 1.4 beta
release by then as well. For what it's worth I have been using it in
several projects recently and it looks solid to me.

Wichert.

--
Wichert Akkerman <wichert[at]wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

tseaver at palladion

Mar 2, 2008, 3:14 PM

Post #2 of 18 (820 views)
Permalink

Re: GenericSetup 1.4 release [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wichert Akkerman wrote:
> The improvements GenericSetup 1.4/trunk has over the 1.3 series are a
> big part of Plone 3.1. With that moving towards it first alpha release
> this Friday it would be practical if there was a GenericSetup 1.4 beta
> release by then as well. For what it's worth I have been using it in
> several projects recently and it looks solid to me.

+1 to creating a beta (including making a 1.4 branch and a 1.4.0b1 tag).

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver[at]palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFHyzTF+gerLs4ltQ4RAjx2AKC9ktMQWOUc6MKy+7J43o83eNn8CQCePkyZ
Jsr+0iHSc/grmzvIRt3U1yg=
=b+wD
-----END PGP SIGNATURE-----

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

wichert at wiggy

Mar 7, 2008, 12:37 AM

Post #3 of 18 (812 views)
Permalink

Re: Re: GenericSetup 1.4 release [In reply to]

Previously Tres Seaver wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Wichert Akkerman wrote:
> > The improvements GenericSetup 1.4/trunk has over the 1.3 series are a
> > big part of Plone 3.1. With that moving towards it first alpha release
> > this Friday it would be practical if there was a GenericSetup 1.4 beta
> > release by then as well. For what it's worth I have been using it in
> > several projects recently and it looks solid to me.
>
> +1 to creating a beta (including making a 1.4 branch and a 1.4.0b1 tag).

I'm happy to see there are no objections. Who is going to make that
release? Jens hasn't responded so perhaps someone else will need to do
that. Tres, can you take care of this?

Wichert.

--
Wichert Akkerman <wichert[at]wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

jens at dataflake

Mar 7, 2008, 1:40 AM

Post #4 of 18 (812 views)
Permalink

Re: Re: GenericSetup 1.4 release [In reply to]

On Mar 7, 2008, at 09:37 , Wichert Akkerman wrote:

> Previously Tres Seaver wrote:
>> -----BEGIN PGP SIGNED MESSAGE-----
>> Hash: SHA1
>>
>> Wichert Akkerman wrote:
>>> The improvements GenericSetup 1.4/trunk has over the 1.3 series
>>> are a
>>> big part of Plone 3.1. With that moving towards it first alpha
>>> release
>>> this Friday it would be practical if there was a GenericSetup 1.4
>>> beta
>>> release by then as well. For what it's worth I have been using it in
>>> several projects recently and it looks solid to me.
>>
>> +1 to creating a beta (including making a 1.4 branch and a 1.4.0b1
>> tag).
>
> I'm happy to see there are no objections. Who is going to make that
> release? Jens hasn't responded so perhaps someone else will need to do
> that. Tres, can you take care of this?

I haven't had any time this week. I may be able to do it some time
today.

jens

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

wichert at wiggy

Mar 7, 2008, 2:00 AM

Post #5 of 18 (813 views)
Permalink

Re: Re: GenericSetup 1.4 release [In reply to]

Previously Jens Vagelpohl wrote:
> On Mar 7, 2008, at 09:37 , Wichert Akkerman wrote:
>
> >Previously Tres Seaver wrote:
> >>-----BEGIN PGP SIGNED MESSAGE-----
> >>Hash: SHA1
> >>
> >>Wichert Akkerman wrote:
> >>>The improvements GenericSetup 1.4/trunk has over the 1.3 series
> >>>are a
> >>>big part of Plone 3.1. With that moving towards it first alpha
> >>>release
> >>>this Friday it would be practical if there was a GenericSetup 1.4
> >>>beta
> >>>release by then as well. For what it's worth I have been using it in
> >>>several projects recently and it looks solid to me.
> >>
> >>+1 to creating a beta (including making a 1.4 branch and a 1.4.0b1
> >>tag).
> >
> >I'm happy to see there are no objections. Who is going to make that
> >release? Jens hasn't responded so perhaps someone else will need to do
> >that. Tres, can you take care of this?
>
> I haven't had any time this week. I may be able to do it some time
> today.

Thanks Jens, that would be much appreciated. FYI I've pushed back the
Plone 3.1 release to Sunday noon CET, so I no longer need this release
today; tomorrow will be fine as well.

Wichert.

--
Wichert Akkerman <wichert[at]wiggy.net> It is simple to make things.
http://www.wiggy.net/ It is hard to make things simple.
_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

jens at dataflake

Mar 7, 2008, 2:10 AM

Post #6 of 18 (811 views)
Permalink

Re: Re: GenericSetup 1.4 release [In reply to]

On Mar 7, 2008, at 11:00 , Wichert Akkerman wrote:
>>> I'm happy to see there are no objections. Who is going to make that
>>> release? Jens hasn't responded so perhaps someone else will need
>>> to do
>>> that. Tres, can you take care of this?
>>
>> I haven't had any time this week. I may be able to do it some time
>> today.
>
> Thanks Jens, that would be much appreciated. FYI I've pushed back the
> Plone 3.1 release to Sunday noon CET, so I no longer need this release
> today; tomorrow will be fine as well.

I'm running the tests on the current GS trunk and see a dozen errors
like the traceback below. Right now my setup is Zope from the 2.10
branch after 2.10.4, maybe a few weeks old. I'm not using buildout or
easy_install, I simply link <GS>/Products/GenericSetup folder into my
instance's Products Folder the old-fashioned way, and then use "bin/
zopectl test" to run the tests. Does anyone else see these?

jens

Error in test
test_runAllImportSteps_unicode_profile_id_creates_reports
(Products.GenericSetup.tests.test_tool.SetupToolTests)
Traceback (most recent call last):
File "/usr/local/zope/src/Zope-2.10-branch/lib/python/Testing/
ZopeTestCase/profiler.py", line 98, in __call__
testMethod()
File "/usr/local/zope/210Instance/Products/GenericSetup/tests/
test_tool.py", line 447, in
test_runAllImportSteps_unicode_profile_id_creates_reports
tool.runAllImportStepsFromProfile(PROFILE_ID)
File "/usr/local/zope/210Instance/Products/GenericSetup/tool.py",
line 390, in runAllImportStepsFromProfile
ignore_dependencies=ignore_dependencies)
File "/usr/local/zope/210Instance/Products/GenericSetup/tool.py",
line 1180, in _runImportStepsFromContext
message = self._doRunImportStep(step, context)
File "/usr/local/zope/210Instance/Products/GenericSetup/tool.py",
line 1094, in _doRunImportStep
return handler(context)
File "/usr/local/zope/210Instance/Products/GenericSetup/
components.py", line 242, in importComponentRegistry
sm = getSiteManager(context.getSite())
File "/usr/local/zope/opt/Zope-2.10-branch/lib/python/zope/
component/_api.py", line 48, in getSiteManager
raise ComponentLookupError(*error.args)
ComponentLookupError: ('Could not adapt', <Folder at /site>,
<InterfaceClass zope.component.interfaces.IComponentLookup>)

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

r.ritz at biologie

Mar 7, 2008, 3:38 AM

Post #7 of 18 (812 views)
Permalink

Re: GenericSetup 1.4 release [In reply to]

Jens Vagelpohl wrote:
>
> On Mar 7, 2008, at 11:00 , Wichert Akkerman wrote:
>>>> I'm happy to see there are no objections. Who is going to make that
>>>> release? Jens hasn't responded so perhaps someone else will need to do
>>>> that. Tres, can you take care of this?
>>>
>>> I haven't had any time this week. I may be able to do it some time
>>> today.
>>
>> Thanks Jens, that would be much appreciated. FYI I've pushed back the
>> Plone 3.1 release to Sunday noon CET, so I no longer need this release
>> today; tomorrow will be fine as well.
>
> I'm running the tests on the current GS trunk and see a dozen errors
> like the traceback below. Right now my setup is Zope from the 2.10
> branch after 2.10.4, maybe a few weeks old. I'm not using buildout or
> easy_install, I simply link <GS>/Products/GenericSetup folder into my
> instance's Products Folder the old-fashioned way, and then use
> "bin/zopectl test" to run the tests. Does anyone else see these?
>

Hi Jens,

I just tried linking a GS trunk checkout into a Zope-2.10.5-final
standalone (build by the Plone Universal installer for Plone 3.0.6
if that matters) and all tests pass.

ritz[at]ritz-laptop:~/Plone-3.0.6/zinstance$ bin/zopectl test -s
Products.GenericSetup
Running tests via: /home/ritz/Plone-3.0.6/Python-2.4.4/bin/python
/home/ritz/Plone-3.0.6/bin/test.py -v --config-file
/home/ritz/Plone-3.0.6/zinstance/etc/zope.conf -s Products.GenericSetup
Parsing /home/ritz/Plone-3.0.6/zinstance/etc/zope.conf
Running tests at level 1
Installing GenericSetup ... done (0.012s)
Running unit tests:
Running:
.....................................................................................................................................................................................................
Ran 197 tests with 0 failures and 0 errors in 0.936 seconds.
Running Products.GenericSetup.testing.ExportImportZCMLLayer tests:
Set up Products.GenericSetup.testing.ExportImportZCMLLayer in 0.359
seconds.
Running:
..........................................................................................................................................................................................
Ran 186 tests with 0 failures and 0 errors in 1.469 seconds.
Tearing down left over layers:
Tear down Products.GenericSetup.testing.ExportImportZCMLLayer in
0.001 seconds.
Total: 383 tests, 0 failures, 0 errors

and

ritz[at]ritz-laptop:~/Plone-3.0.6/zinstance/Products$ svn info GenericSetup/
Path: GenericSetup
URL:
svn://svn.zope.org/repos/main/Products.GenericSetup/trunk/Products/GenericSetup
Repository Root: svn://svn.zope.org/repos/main
Repository UUID: 62d5b8a3-27da-0310-9561-8e5933582275
Revision: 84524
Node Kind: directory
Schedule: normal
Last Changed Author: witsch
Last Changed Rev: 84478
Last Changed Date: 2008-03-05 10:33:15 +0100 (Wed, 05 Mar 2008)

HTH

Raphael

> jens
>
>
> Error in test test_runAllImportSteps_unicode_profile_id_creates_reports
> (Products.GenericSetup.tests.test_tool.SetupToolTests)
> Traceback (most recent call last):
> File
> "/usr/local/zope/src/Zope-2.10-branch/lib/python/Testing/ZopeTestCase/profiler.py",
> line 98, in __call__
> testMethod()
> File
> "/usr/local/zope/210Instance/Products/GenericSetup/tests/test_tool.py",
> line 447, in test_runAllImportSteps_unicode_profile_id_creates_reports
> tool.runAllImportStepsFromProfile(PROFILE_ID)
> File "/usr/local/zope/210Instance/Products/GenericSetup/tool.py", line
> 390, in runAllImportStepsFromProfile
> ignore_dependencies=ignore_dependencies)
> File "/usr/local/zope/210Instance/Products/GenericSetup/tool.py", line
> 1180, in _runImportStepsFromContext
> message = self._doRunImportStep(step, context)
> File "/usr/local/zope/210Instance/Products/GenericSetup/tool.py", line
> 1094, in _doRunImportStep
> return handler(context)
> File
> "/usr/local/zope/210Instance/Products/GenericSetup/components.py", line
> 242, in importComponentRegistry
> sm = getSiteManager(context.getSite())
> File
> "/usr/local/zope/opt/Zope-2.10-branch/lib/python/zope/component/_api.py",
> line 48, in getSiteManager
> raise ComponentLookupError(*error.args)
> ComponentLookupError: ('Could not adapt', <Folder at /site>,
> <InterfaceClass zope.component.interfaces.IComponentLookup>)
>
>
>
> _______________________________________________
> Zope-CMF maillist - Zope-CMF[at]lists.zope.org
> http://mail.zope.org/mailman/listinfo/zope-cmf
>
> See http://collector.zope.org/CMF for bug reports and feature requests
>

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

y.2008 at wcm-solutions

Mar 7, 2008, 4:26 AM

Post #8 of 18 (813 views)
Permalink

Re: GenericSetup 1.4 release [In reply to]

Looks like five.localsitemanager is missing in your setup. Yuppie

Jens Vagelpohl wrote:
> I'm running the tests on the current GS trunk and see a dozen errors
> like the traceback below. Right now my setup is Zope from the 2.10
> branch after 2.10.4, maybe a few weeks old. I'm not using buildout or
> easy_install, I simply link <GS>/Products/GenericSetup folder into my
> instance's Products Folder the old-fashioned way, and then use
> "bin/zopectl test" to run the tests. Does anyone else see these?
>
> jens
>
>
> Error in test test_runAllImportSteps_unicode_profile_id_creates_reports
> (Products.GenericSetup.tests.test_tool.SetupToolTests)
> Traceback (most recent call last):
> File
> "/usr/local/zope/src/Zope-2.10-branch/lib/python/Testing/ZopeTestCase/profiler.py",
> line 98, in __call__
> testMethod()
> File
> "/usr/local/zope/210Instance/Products/GenericSetup/tests/test_tool.py",
> line 447, in test_runAllImportSteps_unicode_profile_id_creates_reports
> tool.runAllImportStepsFromProfile(PROFILE_ID)
> File "/usr/local/zope/210Instance/Products/GenericSetup/tool.py", line
> 390, in runAllImportStepsFromProfile
> ignore_dependencies=ignore_dependencies)
> File "/usr/local/zope/210Instance/Products/GenericSetup/tool.py", line
> 1180, in _runImportStepsFromContext
> message = self._doRunImportStep(step, context)
> File "/usr/local/zope/210Instance/Products/GenericSetup/tool.py", line
> 1094, in _doRunImportStep
> return handler(context)
> File
> "/usr/local/zope/210Instance/Products/GenericSetup/components.py", line
> 242, in importComponentRegistry
> sm = getSiteManager(context.getSite())
> File
> "/usr/local/zope/opt/Zope-2.10-branch/lib/python/zope/component/_api.py",
> line 48, in getSiteManager
> raise ComponentLookupError(*error.args)
> ComponentLookupError: ('Could not adapt', <Folder at /site>,
> <InterfaceClass zope.component.interfaces.IComponentLookup>)

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

jens at dataflake

Mar 7, 2008, 4:51 AM

Post #9 of 18 (813 views)
Permalink

Re: Re: GenericSetup 1.4 release [In reply to]

On Mar 7, 2008, at 13:26 , yuppie wrote:

> Looks like five.localsitemanager is missing in your setup. Yuppie

That's it, great catch!

So what do we do with this apparently undeclared dependency? It's not
mentioned in the top setup.py or in any text documentation in the
package such as in DEPENDENCIES.txt. Where does this need to go?

There's an egg with version 0.3 on the cheeseshop, is that an
acceptable version? I simply linked in what I had here from the
current CMFCore trunk, but that external is against the
five.localsitemanager trunk and the package itself contains no version
information whatsoever (documentation foul!).

jens

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

tseaver at palladion

Mar 7, 2008, 5:11 AM

Post #10 of 18 (813 views)
Permalink

Re: GenericSetup 1.4 release [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jens Vagelpohl wrote:
> On Mar 7, 2008, at 13:26 , yuppie wrote:
>
>> Looks like five.localsitemanager is missing in your setup. Yuppie
>
> That's it, great catch!

I got bitten by the same issue a couple of weeks ago, and dropped the
ball on getting the tests runnable via 'setup.py test'.

> So what do we do with this apparently undeclared dependency? It's not
> mentioned in the top setup.py or in any text documentation in the
> package such as in DEPENDENCIES.txt. Where does this need to go?
>
> There's an egg with version 0.3 on the cheeseshop, is that an
> acceptable version? I simply linked in what I had here from the
> current CMFCore trunk, but that external is against the
> five.localsitemanager trunk and the package itself contains no version
> information whatsoever (documentation foul!).

Installing the cheeseshop version makes the tests pass. The cheeseshop
should have a source distribution, rather than an egg, for that package,
however.

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver[at]palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH0T8S+gerLs4ltQ4RAtjyAKCwNJhUhUkFscZK7yId92RkJSmjowCfcdCP
nbktWxMVCsoyamGn6t2pnPA=
=Kxtz
-----END PGP SIGNATURE-----

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

tseaver at palladion

Mar 7, 2008, 5:11 AM

Post #11 of 18 (813 views)
Permalink

Re: GenericSetup 1.4 release [In reply to]

jens at dataflake

Mar 7, 2008, 5:41 AM

Post #12 of 18 (808 views)
Permalink

Re: Re: GenericSetup 1.4 release [In reply to]

On Mar 7, 2008, at 14:11 , Tres Seaver wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Jens Vagelpohl wrote:
>> On Mar 7, 2008, at 13:26 , yuppie wrote:
>>
>>> Looks like five.localsitemanager is missing in your setup. Yuppie
>>
>> That's it, great catch!
>
> I got bitten by the same issue a couple of weeks ago, and dropped the
> ball on getting the tests runnable via 'setup.py test'.

I'll keep running tests within an instance with "zopectl" for now and
consider thinks OK when that works.

jens

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

jens at dataflake

Mar 7, 2008, 6:15 AM

Post #13 of 18 (813 views)
Permalink

Re: Re: GenericSetup 1.4 release [In reply to]

On Mar 3, 2008, at 00:14 , Tres Seaver wrote:

> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Wichert Akkerman wrote:
>> The improvements GenericSetup 1.4/trunk has over the 1.3 series are a
>> big part of Plone 3.1. With that moving towards it first alpha
>> release
>> this Friday it would be practical if there was a GenericSetup 1.4
>> beta
>> release by then as well. For what it's worth I have been using it in
>> several projects recently and it looks solid to me.
>
> +1 to creating a beta (including making a 1.4 branch and a 1.4.0b1
> tag).

There's a tarball/zipfile here:

http://www.zope.org/Products/GenericSetup/GenericSetup-1.4.0-beta

and an egg here:

http://pypi.python.org/pypi/Products.GenericSetup

Please take a look at the egg, if that's what you will be using, and
let me know if it's OK (contains all files, no extraneous files, etc)
since I'm not very well versed in doing the whole egg thing.

jens

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

plone at hannosch

Mar 7, 2008, 8:28 AM

Post #14 of 18 (810 views)
Permalink

Re: GenericSetup 1.4 release [In reply to]

Jens Vagelpohl wrote:
> There's an egg with version 0.3 on the cheeseshop, is that an acceptable
> version? I simply linked in what I had here from the current CMFCore
> trunk, but that external is against the five.localsitemanager trunk and
> the package itself contains no version information whatsoever
> (documentation foul!).

The CMF 2.1 branch uses the five.lsm 0.3 tag, which is identical to the
trunk, except that trunk states it is going to be version 0.4.

On PyPi there are both an egg as well as a source distribution for the
0.3 release.

The CMF trunk currently points to the five.lsm trunk, which doesn't have
a version information inside it, as it only uses a part of the actual
package. The version information is in the root setup.py, whereas CMF
only pulls in the src/five/localsitemanager part of it.

Why did we do the above at all? Because we didn't want to require anyone
to install a package for the CMF 2.1 line on top of extracting the
tarball into the Products folder. For CMF trunk I personally think it is
OK, to state a proper dependency in setup.py for both CMF and
GenericSetup now and remove the five.lsm inclusion hack from CMFCore.

Hanno

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

jens at dataflake

Mar 7, 2008, 9:08 AM

Post #15 of 18 (809 views)
Permalink

Re: Re: GenericSetup 1.4 release [In reply to]

On Mar 7, 2008, at 17:28 , Hanno Schlichting wrote:

> The CMF trunk currently points to the five.lsm trunk, which doesn't
> have a version information inside it, as it only uses a part of the
> actual package. The version information is in the root setup.py,
> whereas CMF only pulls in the src/five/localsitemanager part of it.

Other packages I know get around this problem by putting version
infomation into a proper version.txt file inside the actual code
folder and then reading it out to get at the value inside the toplevel
setup.py. If there's no specific reason why this is bad I'd suggest
that here as well.

> Why did we do the above at all? Because we didn't want to require
> anyone to install a package for the CMF 2.1 line on top of
> extracting the tarball into the Products folder. For CMF trunk I
> personally think it is OK, to state a proper dependency in setup.py
> for both CMF and GenericSetup now and remove the five.lsm inclusion
> hack from CMFCore.

The dependency should be in setup.py and DEPENDENCIES.txt inside
CMFCore, it already exists there, I looked. I'm in favor of removing
the hack on the CMFCore trunk.

jens

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

tseaver at palladion

Mar 7, 2008, 9:52 AM

Post #16 of 18 (812 views)
Permalink

Re: GenericSetup 1.4 release [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hanno Schlichting wrote:
> Jens Vagelpohl wrote:
>> There's an egg with version 0.3 on the cheeseshop, is that an acceptable
>> version? I simply linked in what I had here from the current CMFCore
>> trunk, but that external is against the five.localsitemanager trunk and
>> the package itself contains no version information whatsoever
>> (documentation foul!).
>
> The CMF 2.1 branch uses the five.lsm 0.3 tag, which is identical to the
> trunk, except that trunk states it is going to be version 0.4.
>
> On PyPi there are both an egg as well as a source distribution for the
> 0.3 release.
>
> The CMF trunk currently points to the five.lsm trunk, which doesn't have
> a version information inside it, as it only uses a part of the actual
> package. The version information is in the root setup.py, whereas CMF
> only pulls in the src/five/localsitemanager part of it.
>
> Why did we do the above at all? Because we didn't want to require anyone
> to install a package for the CMF 2.1 line on top of extracting the
> tarball into the Products folder. For CMF trunk I personally think it is
> OK, to state a proper dependency in setup.py for both CMF and
> GenericSetup now and remove the five.lsm inclusion hack from CMFCore.

+1.

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver[at]palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH0YDY+gerLs4ltQ4RAqsCAJ44QyrLAeMlrEIyf0Iiw4Gszw6i/wCfRF7T
z0ZhK+jTRjKCuuFm1GQgrNQ=
=B/Vv
-----END PGP SIGNATURE-----

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

tseaver at palladion

Mar 7, 2008, 9:52 AM

Post #17 of 18 (812 views)
Permalink

Re: GenericSetup 1.4 release [In reply to]

tseaver at palladion

Mar 7, 2008, 9:53 AM

Post #18 of 18 (811 views)
Permalink

Re: GenericSetup 1.4 release [In reply to]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Jens Vagelpohl wrote:
> On Mar 7, 2008, at 17:28 , Hanno Schlichting wrote:
>
>> The CMF trunk currently points to the five.lsm trunk, which doesn't
>> have a version information inside it, as it only uses a part of the
>> actual package. The version information is in the root setup.py,
>> whereas CMF only pulls in the src/five/localsitemanager part of it.
>
> Other packages I know get around this problem by putting version
> infomation into a proper version.txt file inside the actual code
> folder and then reading it out to get at the value inside the toplevel
> setup.py. If there's no specific reason why this is bad I'd suggest
> that here as well.
>
>
>> Why did we do the above at all? Because we didn't want to require
>> anyone to install a package for the CMF 2.1 line on top of
>> extracting the tarball into the Products folder. For CMF trunk I
>> personally think it is OK, to state a proper dependency in setup.py
>> for both CMF and GenericSetup now and remove the five.lsm inclusion
>> hack from CMFCore.
>
> The dependency should be in setup.py and DEPENDENCIES.txt inside
> CMFCore, it already exists there, I looked. I'm in favor of removing
> the hack on the CMFCore trunk.

I added the dependency in GenericSetup-trunk's setup.py and
DEPENDENCIES.txt as well (committed this morning).

Tres.
- --
===================================================================
Tres Seaver +1 540-429-0999 tseaver[at]palladion.com
Palladion Software "Excellence by Design" http://palladion.com
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFH0YEN+gerLs4ltQ4RAim7AKDdFIkOcLglbHf2DiL7Dksoi/Yf4QCgoTa9
sSr2u24j3s+JIjNnTeT1suc=
=SGVc
-----END PGP SIGNATURE-----

_______________________________________________
Zope-CMF maillist - Zope-CMF[at]lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

See http://collector.zope.org/CMF for bug reports and feature requests

Index | Next | Previous | View Threaded

Interested in having your list archived? Contact lists@gossamer-threads.com