grokproject and svn

[Sebastian Ware]

when using

   --svn-repository=REPOS

The egg-info directory is added to version control
   src/yourproject.egg-info/
however in the version control docs
  http://grok.zope.org/documentation/how-to/placing-your-grok-project-under-version-control

it says that this info shouldn't be version controlled

a) What is correct?

b) I think --svn-repository=REPOS should be promoted in the tutorial.  
It signals good practice.

Mvh Sebastian

_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

[Philipp von Weitershausen]

Sebastian Ware wrote:

> when using
>
>   --svn-repository=REPOS
>
> The egg-info directory is added to version control
>   src/yourproject.egg-info/
> however in the version control docs
>  http://grok.zope.org/documentation/how-to/placing-your-grok-project-under-version-control 
>
>
> it says that this info shouldn't be version controlled
>
> a) What is correct?

Opinions differ. Some think it should be checked in. The use case for
this that I've heard is that the egg-info may contain stuff that's not
auto-generated from setup.py, such as locale data. But since we put all
of our package data into the packages themselves and thus our egg-info
completely generated from setup.py, I see little point in checking it in.

Fact is, it's PasteScript checking things in for us, so unless we hack
PasteScript, we'll have to live with this for now.

> b) I think --svn-repository=REPOS should be promoted in the tutorial. It
> signals good practice.

Maybe.
_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

[Maurits van Rees-3]

Philipp von Weitershausen, on 2008-05-18:
>> b) I think --svn-repository=REPOS should be promoted in the tutorial. It
>> signals good practice.
>
> Maybe.

For people just playing around with Grok for trying it this is not
really necessary.  If we add this to the tutorial we also need to
point people to a subversion repository where they can check things in
or how to create a repository themselves, which increases the scope of
the tutorial again.

I'm not really against it, but it would be more than just a one-liner.

--
Maurits van Rees | http://maurits.vanrees.org/
            Work | http://zestsoftware.nl/
"This is your day, don't let them take it away." [Barlow Girl]

_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

[Sebastian Ware]

19 maj 2008 kl. 11.46 skrev Maurits van Rees:

> Philipp von Weitershausen, on 2008-05-18:
>>> b) I think --svn-repository=REPOS should be promoted in the  
>>> tutorial. It
>>> signals good practice.
>>
>> Maybe.
>
> For people just playing around with Grok for trying it this is not
> really necessary.  If we add this to the tutorial we also need to
> point people to a subversion repository where they can check things in
> or how to create a repository themselves, which increases the scope of
> the tutorial again.
>
> I'm not really against it, but it would be more than just a one-liner.

Maybe so, but this feature makes version control in every project a no-
brainer. Doing the initial import  manually is a distraction that  
tends to put me off.

Mvh Sebastian

_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

[Martijn Faassen-2]

Sebastian Ware wrote:

> when using
>
>   --svn-repository=REPOS
>
> The egg-info directory is added to version control
>   src/yourproject.egg-info/
> however in the version control docs
>  http://grok.zope.org/documentation/how-to/placing-your-grok-project-under-version-control 
>
> it says that this info shouldn't be version controlled
>
> a) What is correct?

While Philipp mentions that there are advocates to both practices, I
think we can clearly identify the Zope camp as *not* doing this. I think
therefore we ideally we shouldn't be doing this.

I understood from Philipp that this requires a change somewhere in
paste... What's involved?

> b) I think --svn-repository=REPOS should be promoted in the tutorial. It
> signals good practice.

It should indeed be mentioned in *some* documentation, either the
tutorial or the developer notes.

Regards,

Martijn

_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

[whit morriss-2]

Philipp von Weitershausen wrote:

> Sebastian Ware wrote:
>> when using
>>
>>   --svn-repository=REPOS
>>
>> The egg-info directory is added to version control
>>   src/yourproject.egg-info/
>> however in the version control docs
>>  http://grok.zope.org/documentation/how-to/placing-your-grok-project-under-version-control 
>>
>>
>> it says that this info shouldn't be version controlled
>>
>> a) What is correct?
>
> Opinions differ. Some think it should be checked in. The use case for
> this that I've heard is that the egg-info may contain stuff that's not
> auto-generated from setup.py, such as locale data. But since we put all
> of our package data into the packages themselves and thus our egg-info
> completely generated from setup.py, I see little point in checking it in.
>
> Fact is, it's PasteScript checking things in for us, so unless we hack
> PasteScript, we'll have to live with this for now.
>

there is a reason for this... paste and pastescript save plugin metadata
in package info to allow for rerunning of template plugins.  This is the
major way of allowing plugins that are used to create items within a
package after package is created.  zopeskel in the collective utilizes
this iirc.

-w

_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev

[Reinout van Rees]

whit morriss schreef:

> there is a reason for this... paste and pastescript save plugin metadata
> in package info to allow for rerunning of template plugins.  This is the
> major way of allowing plugins that are used to create items within a
> package after package is created.  zopeskel in the collective utilizes
> this iirc.

Yes, the archetype template of zopeskel. (At least not all of them, like
the buildout templates or so).


Reinout

--
Reinout van Rees          Blog: http://vanrees.org/weblog/
reinout@...          Work: http://zestsoftware.nl/
http://vanrees.org          Video: http://reinout.blip.tv/

_______________________________________________
Grok-dev mailing list
Grok-dev@...
http://mail.zope.org/mailman/listinfo/grok-dev