[zc.buildout] find-links does not deal with two-level hierarchy
Hi,
we have a local fileserver with a two-level hierarchy for egg -something like:
haufe.eggserver +--- haufe.eggserver-0.1.0.egg +--- haufe.recipe.svnsetup +--- ....
easy_install -i http://our-server/egg haufe.recipe.svnsetup works fine with this two-level hierarchy.
Using the URL within the find-links option of my buildout.cfg does not work (Error: Could not find a distribution...) for a part with recipe=haufe.recipe.svnsetup.
Bug or feature?
Andreas
At 02:26 PM 3/7/2008 +0100, Andreas Jung wrote:
Hi,
we have a local fileserver with a two-level hierarchy for egg -something like:
haufe.eggserver +--- haufe.eggserver-0.1.0.egg +--- haufe.recipe.svnsetup +--- ....
easy_install -i http://our-server/egg haufe.recipe.svnsetup works fine with this two-level hierarchy.
Using the URL within the find-links option of my buildout.cfg does not work (Error: Could not find a distribution...) for a part with recipe=haufe.recipe.svnsetup.
Bug or feature?
By design -- easy_install doesn't want to be a general-purpose web spider.
If you want your index to work with find-links, you'll need to either dump it all in one level (and use -f instead of -i), or else put 2nd-level links in your find-links.
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Phillip J. Eby wrote:
At 02:26 PM 3/7/2008 +0100, Andreas Jung wrote:
Hi,
we have a local fileserver with a two-level hierarchy for egg -something like:
haufe.eggserver +--- haufe.eggserver-0.1.0.egg +--- haufe.recipe.svnsetup +--- ....
easy_install -i http://our-server/egg haufe.recipe.svnsetup works fine with this two-level hierarchy.
Using the URL within the find-links option of my buildout.cfg does not work (Error: Could not find a distribution...) for a part with recipe=haufe.recipe.svnsetup.
Bug or feature?
By design -- easy_install doesn't want to be a general-purpose web spider.
If you want your index to work with find-links, you'll need to either dump it all in one level (and use -f instead of -i), or else put 2nd-level links in your find-links.
When you use 'easy_install -i URL', you are using an *index*, which is different than using *find links* (the '-f' options). If zc.buildout were able to express "use this package index, but only for this target egg", then that would be the equivalent spelling.
Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com
On Mar 7, 2008, at 12:58 PM, Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Phillip J. Eby wrote:
At 02:26 PM 3/7/2008 +0100, Andreas Jung wrote:
Hi,
we have a local fileserver with a two-level hierarchy for egg - something like:
haufe.eggserver +--- haufe.eggserver-0.1.0.egg +--- haufe.recipe.svnsetup +--- ....
easy_install -i http://our-server/egg haufe.recipe.svnsetup works fine with this two-level hierarchy.
Using the URL within the find-links option of my buildout.cfg does not work (Error: Could not find a distribution...) for a part with recipe=haufe.recipe.svnsetup.
Bug or feature?
By design -- easy_install doesn't want to be a general-purpose web spider.
If you want your index to work with find-links, you'll need to either dump it all in one level (and use -f instead of -i), or else put 2nd-level links in your find-links.
When you use 'easy_install -i URL', you are using an *index*, which is different than using *find links* (the '-f' options). If zc.buildout were able to express "use this package index, but only for this target egg", then that would be the equivalent spelling.
zc.buildout does let you specify an index for an individual part/egg.
I fail to see how that is an equivalent spelling.
Jim
-- Jim Fulton Zope Corporation
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Jim Fulton wrote:
On Mar 7, 2008, at 12:58 PM, Tres Seaver wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Phillip J. Eby wrote:
At 02:26 PM 3/7/2008 +0100, Andreas Jung wrote:
Hi,
we have a local fileserver with a two-level hierarchy for egg - something like:
haufe.eggserver +--- haufe.eggserver-0.1.0.egg +--- haufe.recipe.svnsetup +--- ....
easy_install -i http://our-server/egg haufe.recipe.svnsetup works fine with this two-level hierarchy.
Using the URL within the find-links option of my buildout.cfg does not work (Error: Could not find a distribution...) for a part with recipe=haufe.recipe.svnsetup.
Bug or feature?
By design -- easy_install doesn't want to be a general-purpose web spider.
If you want your index to work with find-links, you'll need to either dump it all in one level (and use -f instead of -i), or else put 2nd-level links in your find-links.
When you use 'easy_install -i URL', you are using an *index*, which is different than using *find links* (the '-f' options). If zc.buildout were able to express "use this package index, but only for this target egg", then that would be the equivalent spelling.
zc.buildout does let you specify an index for an individual part/egg.
I didn't know that: I believed the "there can be only one index" meme which I heard during the KGS discussion.
I fail to see how that is an equivalent spelling.
If each a buildout can customize the index URL for each egg it installs, then Andreas can have what he wants, which is a way to install an egg in the same way that 'easy_install -i' does. 'find-links' is a distraction, in this case, because it is not the same as 'easy_install - -i' (it is equivalent to 'easy_install -f').
Tres. - -- =================================================================== Tres Seaver +1 540-429-0999 tseaver@palladion.com Palladion Software "Excellence by Design" http://palladion.com
participants (4)
-
Andreas Jung -
Jim Fulton -
Phillip J. Eby -
Tres Seaver