Relative path support for z3c.recipe.paster?

[Jonathan Ballet-5]

Hi,

Since zc.recipe.egg 1.2.0, there's an option to generate scripts which
contains relative paths to eggs installed in the eggs/ directory [1]
This is very handy if you want to move your buildout around, without
needing to relaunch the whole buildout process.

What do maintainers of z3c.recipe.paster think if I propose a patch
which add this option (or something else) to support the same thing
for this recipe?
Actually, this can be a relatively minor change, since the recipe
already use zc.recipe.egg, which means it only has to pass the
corresponding option to this one.

Thoughts?

Cheers,

 Jonathan

[1] : http://pypi.python.org/pypi/zc.recipe.egg#relative-egg-paths
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
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 )

[Roger Ineichen]

Hi Jonathan

> Betreff: [Zope-dev] Relative path support for z3c.recipe.paster?
>
> Hi,
>
> Since zc.recipe.egg 1.2.0, there's an option to generate
> scripts which contains relative paths to eggs installed in
> the eggs/ directory [1] This is very handy if you want to
> move your buildout around, without needing to relaunch the
> whole buildout process.
>
> What do maintainers of z3c.recipe.paster think if I propose a
> patch which add this option (or something else) to support
> the same thing for this recipe?
> Actually, this can be a relatively minor change, since the
> recipe already use zc.recipe.egg, which means it only has to
> pass the corresponding option to this one.
>
> Thoughts?

In general any improvment is welcome as long as there is no bad
sideffect. I do not know this option and do not understand what
you mean with moving buildout around.

I guess this is nothing which is needed in a productive setup.

Anyway, if there is no sideffect like larger processing time
in prodction use just for provide a fancy feature, you are very
welcome to improve and implement usefull things ;-)

Regards
Roger Ineichen

> Cheers,
>
>  Jonathan
>
> [1] : http://pypi.python.org/pypi/zc.recipe.egg#relative-egg-paths
> _______________________________________________
> Zope-Dev maillist  -  Zope-Dev@...
> 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 maillist  -  Zope-Dev@...
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 )

[Jonathan Ballet-5]

Hi Roger,

On Wed, Nov 4, 2009 at 5:15 PM, Roger Ineichen <dev@...> wrote:
> Hi Jonathan
>
> In general any improvment is welcome as long as there is no bad
> sideffect. I do not know this option and do not understand what
> you mean with moving buildout around.

By "moving buildout around", I mean: I generate a buildout in a
directory, let's say /home/foo/prod/1.0 on the host FOO, and I would
like to be able to copy the result of the buildout on the host BAR, in
the directory /var/run/bar/ and be able to just run ./bin/paster and
voilà!
That's why I would like to have relative paths.

> Anyway, if there is no sideffect like larger processing time
> in prodction use just for provide a fancy feature, you are very
> welcome to improve and implement usefull things ;-)

Ok, I don't think the modification will have such side effects, so I
will propose a patch for this then :)

Cheers,

 Jonathan
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
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 )

[Adam Groszer-2]

Hello Jonathan,

bin/buildout -N does not fit you?

Wednesday, November 4, 2009, 5:50:45 PM, you wrote:

JB> Hi Roger,

JB> On Wed, Nov 4, 2009 at 5:15 PM, Roger Ineichen <dev@...> wrote:
>> Hi Jonathan
>>
>> In general any improvment is welcome as long as there is no bad
>> sideffect. I do not know this option and do not understand what
>> you mean with moving buildout around.

JB> By "moving buildout around", I mean: I generate a buildout in a
JB> directory, let's say /home/foo/prod/1.0 on the host FOO, and I would
JB> like to be able to copy the result of the buildout on the host BAR, in
JB> the directory /var/run/bar/ and be able to just run ./bin/paster and
JB> voilà!
JB> That's why I would like to have relative paths.

>> Anyway, if there is no sideffect like larger processing time
>> in prodction use just for provide a fancy feature, you are very
>> welcome to improve and implement usefull things ;-)

JB> Ok, I don't think the modification will have such side effects, so I
JB> will propose a patch for this then :)

JB> Cheers,

JB>  Jonathan
JB> _______________________________________________
JB> Zope-Dev maillist  -  Zope-Dev@...
JB> https://mail.zope.org/mailman/listinfo/zope-dev
JB> **  No cross posts or HTML encoding!  **
JB> (Related lists -
JB>  https://mail.zope.org/mailman/listinfo/zope-announce
JB>  https://mail.zope.org/mailman/listinfo/zope )


--
Best regards,
 Adam GROSZER                            mailto:agroszer@...
--
Quote of the day:
The best discipline, maybe the only discipline that really works, is self-discipline.
- Walter Kiechel III

_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
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 )

[Jonathan Ballet-5]

Hi Adam,

On Wed, Nov 4, 2009 at 7:11 PM, Adam GROSZER <agroszer@...> wrote:
> Hello Jonathan,
>
> bin/buildout -N does not fit you?

In fact, we have very strong constraints where our buildout's results
are ran : most of our customers deploy this package on host which
don't have freely access to outside. Running "bin/buildout -N" is out
of the question since this will certainly fail. Maybe "bin/buildout
-o" could work for us.

Currently, we are testing if we can ship the result of a buildout
without re-running the buildout on the target host. If we could have
relative paths everywhere in the buildout, this would certainly make
the process less painful for us :)

Anyway, I started to look a bit at z3c.recipe.paster, and it seems a
little bit more complicated than I originally found, since it involved
copying some more code from zc.recipe.egg which need to be passed to
zc.buildout.easy_install.script() call... I'll keep you informed.

Best regards,

 Jonathan
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
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 )

[wichert]

On 11/5/09 14:18 , Jonathan Ballet wrote:

> Hi Adam,
>
> On Wed, Nov 4, 2009 at 7:11 PM, Adam GROSZER<agroszer@...>  wrote:
>> Hello Jonathan,
>>
>> bin/buildout -N does not fit you?
>
> In fact, we have very strong constraints where our buildout's results
> are ran : most of our customers deploy this package on host which
> don't have freely access to outside. Running "bin/buildout -N" is out
> of the question since this will certainly fail. Maybe "bin/buildout
> -o" could work for us.

Isn't zc.sourcerelease is designed for exactly those types of situations?

Wichert.
_______________________________________________
Zope-Dev maillist  -  Zope-Dev@...
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 )