Re: [Zope-CMF] Re: License file question

2008-05-29 Thread Wichert Akkerman
Previously Maurits van Rees wrote:
 Wichert Akkerman, on 2008-05-29:
  Previously Philipp von Weitershausen wrote:
  But personally I like having it inside the main
  folder, so in your example above it would be
  incf.applications/incf/applications/HISTORY.txt 
  
  There's some benefit to that because it'll be part of the egg.
 
  You probably want to use a MANIFEST.in anyway and that can easily be
  used to include everything in doc/ or other places.
 
 A 'python setup.py sdist' will include the docs directory, as long as
 it is in subversion (and has at least one file in it).

And when someone installs from that sdist and there is no MANIFEST.in
you suddenly end up with installs which are missing data files, zcml
files or other things. 

Wichert.

-- 
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/   It is hard to make things simple.
___
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

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


Re: [Zope-CMF] Re: License file question

2008-05-29 Thread Philipp von Weitershausen

On 29 May 2008, at 11:27 , Wichert Akkerman wrote:

Previously Philipp von Weitershausen wrote:

But personally I like having it inside the main
folder, so in your example above it would be
incf.applications/incf/applications/HISTORY.txt


There's some benefit to that because it'll be part of the egg.


You probably want to use a MANIFEST.in anyway and that can easily be
used to include everything in doc/ or other places.


Good point!

___
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

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


Re: [Zope-CMF] Re: License file question

2008-05-29 Thread Wichert Akkerman
Previously Philipp von Weitershausen wrote:
 But personally I like having it inside the main
 folder, so in your example above it would be
 incf.applications/incf/applications/HISTORY.txt 
 
 There's some benefit to that because it'll be part of the egg.

You probably want to use a MANIFEST.in anyway and that can easily be
used to include everything in doc/ or other places.

Wichert.

-- 
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/   It is hard to make things simple.
___
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

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


Re: [Zope-CMF] Re: License file question

2008-05-29 Thread Wichert Akkerman
Previously Maurits van Rees wrote:
 Wichert Akkerman, on 2008-05-29:
  Previously Maurits van Rees wrote:
  Wichert Akkerman, on 2008-05-29:
   Previously Philipp von Weitershausen wrote:
   But personally I like having it inside the main
   folder, so in your example above it would be
   incf.applications/incf/applications/HISTORY.txt 
   
   There's some benefit to that because it'll be part of the egg.
  
   You probably want to use a MANIFEST.in anyway and that can easily be
   used to include everything in doc/ or other places.
  
  A 'python setup.py sdist' will include the docs directory, as long as
  it is in subversion (and has at least one file in it).
 
  And when someone installs from that sdist and there is no MANIFEST.in
  you suddenly end up with installs which are missing data files, zcml
  files or other things. 
 
 Is there a difference in that regard between easy installing an sdist
 or a bdist_egg?  I would think/hope that the end result is the same.

Yes. If you make the bdist_egg from a svn checkout it includes all files
that are in subversion. If you make an egg from something else like a
sdist or a svn export that does not happen (since the svn information is
not available).

Wichert.

-- 
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/   It is hard to make things simple.
___
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

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


Re: [Zope-CMF] Re: License file question

2008-05-29 Thread Jens Vagelpohl


On May 29, 2008, at 04:19 , Philipp von Weitershausen wrote:

[1] 
http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/maintaining-software.txt


Ah, good resource, thanks for pointing that out.

Thanks to everyone for the input. I'll go with putting the license  
file right with the software instead of into a docs folder at the top  
where setup.py resides. I find it more intuitive to have all  
documentation where the software is, and leave the egg scaffolding  
in a state where you don't have to touch anything up high once it's  
working.


jens

___
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

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


Re: [Zope-CMF] Re: License file question

2008-05-29 Thread Wichert Akkerman
Previously Maurits van Rees wrote:
 Wichert Akkerman, on 2008-05-29:
  Previously Maurits van Rees wrote:
  Wichert Akkerman, on 2008-05-29:
   Previously Maurits van Rees wrote:
   Wichert Akkerman, on 2008-05-29:
Previously Philipp von Weitershausen wrote:
But personally I like having it inside the main
folder, so in your example above it would be
incf.applications/incf/applications/HISTORY.txt 

There's some benefit to that because it'll be part of the egg.
   
You probably want to use a MANIFEST.in anyway and that can easily be
used to include everything in doc/ or other places.
   
   A 'python setup.py sdist' will include the docs directory, as long as
   it is in subversion (and has at least one file in it).
  
   And when someone installs from that sdist and there is no MANIFEST.in
   you suddenly end up with installs which are missing data files, zcml
   files or other things. 
  
  Is there a difference in that regard between easy installing an sdist
  or a bdist_egg?  I would think/hope that the end result is the same.
 
  Yes. If you make the bdist_egg from a svn checkout it includes all files
  that are in subversion. If you make an egg from something else like a
  sdist or a svn export that does not happen (since the svn information is
  not available).
 
 Without a MANIFEST.in, the egg resulting from an sdist that is
 easy_installed is the same as a bdist_egg, right?  Indeed when I try
 that for plone.portlet.static this is the case.  So having a
 MANIFEST.in makes no real difference in that regard.

I'm not sure what you mean. The basic algorihm is:

- MANIFEST is used to determine what is installed, or
- subversion workingcopy information is used to determine what is installed, or
- a default ruleset is used

This algorithm is used at the moment a 'binary installation' is made,
which is either when you build an egg using setup.py bdist_egg or when
you install an egg from source (ie from a sdist or an unpacked tree).

You can find full documentation on
http://peak.telecommunity.com/DevCenter/setuptools

Wichert.

-- 
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/   It is hard to make things simple.
___
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

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


Re: [Zope-CMF] Re: License file question

2008-05-29 Thread Wichert Akkerman
Previously Maurits van Rees wrote:
 Jens Vagelpohl, on 2008-05-29:
 
  On May 29, 2008, at 04:19 , Philipp von Weitershausen wrote:
  [1] 
  http://svn.zope.org/*checkout*/Sandbox/philikon/foundation/maintaining-software.txt
 
  Ah, good resource, thanks for pointing that out.
 
  Thanks to everyone for the input. I'll go with putting the license  
  file right with the software instead of into a docs folder at the top  
  where setup.py resides. I find it more intuitive to have all  
  documentation where the software is, and leave the egg scaffolding  
  in a state where you don't have to touch anything up high once it's  
  working.
 
 Suits me fine.  Anyone in favour of updating the ZopeSkel templates to
 fit that pattern?  (Sorry, bit out of topic here on the cmf list as
 there are no cmf skeletons there.  Care to add one? :-))

-1

I want all documentation to be the first thing I see when I unpack
something. I don't want to be forced to delve into 3 or 4
subdirectories.

Wichert.

-- 
Wichert Akkerman [EMAIL PROTECTED]It is simple to make things.
http://www.wiggy.net/   It is hard to make things simple.
___
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

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


Re: [Zope-CMF] Re: License file question

2008-05-29 Thread Jens Vagelpohl


On May 29, 2008, at 08:34 , Wichert Akkerman wrote:


Previously Maurits van Rees wrote:
Suits me fine.  Anyone in favour of updating the ZopeSkel templates  
to

fit that pattern?  (Sorry, bit out of topic here on the cmf list as
there are no cmf skeletons there.  Care to add one? :-))


-1

I want all documentation to be the first thing I see when I unpack
something. I don't want to be forced to delve into 3 or 4
subdirectories.


This is veering off course a little, a discussion about ZopeSkel  
handles this should probabably happen elsewhere ;-)  I know how I'll  
proceed with the CMF packages.


jens



___
Zope-CMF maillist  -  Zope-CMF@lists.zope.org
http://mail.zope.org/mailman/listinfo/zope-cmf

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