Raphael Ritz, on 2008-05-29:
Not sure whether that's following best practice but here is
how paster/zopeskel generate this at the moment (this is taken
from a custom add-on I'm currently working on):
[EMAIL PROTECTED]:~/dev/paster/incf.applications/trunk$ ls
docs incf
Jens Vagelpohl wrote:
Hi Jens,
Just wondering: Now that we are splitting the CMF down into its
constituent packages and people don't need to get the old-fashioned
tarball, do we need to have a copy of the LICENSE.txt file in every
package?
I'd think so, yes.
And if yes, where would it
Maurits van Rees wrote:
Raphael Ritz, on 2008-05-29:
Not sure whether that's following best practice but here is
how paster/zopeskel generate this at the moment (this is taken
from a custom add-on I'm currently working on):
[EMAIL PROTECTED]:~/dev/paster/incf.applications/trunk$ ls
docs incf
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
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
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
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
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
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
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
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
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
Wichert Akkerman, on 2008-05-29:
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
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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Wichert Akkerman wrote:
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
16 matches
Mail list logo