Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Fri, Jun 20, 2003 at 10:58:54AM -0400, Chris McDonough wrote: > I'm afraid I'll need to understand more about what debian considers > "architecture dependent". Can you provide details about what this > means? [There is nothing special about Debian and architecture dependent files] Dependent is any file which cannot be used on a different hardware architecture. Compiled 'c' code is architecture dependent. Python compiled source (.pyc, .pyo), text files of any sort and almost all kinds of data files like sounds, images or videos do behave the same, regardless the hardware architecture they are installed on: thus they are architecture independent. I tryed any conbination of setup.py options to make it work, but i was not succesful: that led me to think this feature was not considered. thanks, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Fri, Jun 20, 2003 at 08:57:34AM +0200, PieterB wrote: > On the other hand some packages (such as my zopetest, or other > rpm-alike things), may require other things. I like A-A-P, because > I think that would make my installerfiles much cleaner. Aap has > integrated support to fail if a program returns an error, which > isn't the case for shell scripts. Try use #!/bin/sh -e instead of #!/bin/sh alone. > Make also has error support and can be used to define 'modules'/'tasks' but > it's terrible to create something similar to > http://cvs.zope.org/NZO_SiteLayout/buildout_zope_sandbox?cvsroot=Zope.org in > Makefiles. If you need i can port a script like that to Makefile without that much work. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Fri, Jun 20, 2003 at 03:38:53PM +1000, Adrian van den Dries wrote: > > Well, as we all know, shell scripting kinda blows. There is no way that > > I know of to portably use an array in shell, and I wanted to eventually > > make it possible to use something other than bash to run the configure > > script (bash has arrays, but I'm not sure if bourne shell does). > > You may be interested in Kenneth Almquist's ash (aka dash in Debian): If you aim portability, I would suggest to use only standard tools: if you want to make an installation procedure portable trough various systems and architectures, you should only use strict sh scripting, Makefile and other tools which may be considered to be installed by default on any unix system. Speaking of Zope, python is also acceptable: you need python to run Zope, and so it is reasonable that you use a language that is supposed to be available on the target system. I would not use bash or any non standard sh derivation, because they might not be available. If you start to feel the need of some more complex constructs than those available with sh, than you should consider to use python. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Thu, Jun 19, 2003 at 10:59:29AM -0400, Chris McDonough wrote: > So, in any case, given that the ZC source tarball installer will not > attempt to manage multiple instances (we'll leave that to Luca) here are > the requirements I've gathered so far: > > - Add a --doc flag to configure > - Add a --skel flag to configure (is this a common pattern?) > > Possibly: > > - Make it possible to install Zope libraries into the site-packages > directory of the Python that invokes Zope's setup.py instead of into > software_home/lib/python. > > Am I missing anything? I'd like to have the possibility to install any architecture dependant files in an different tree. thanks, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Wed, Jun 18, 2003 at 03:08:12PM -0400, Chris McDonough wrote: > If you want to change your Zope controller to work with 2.7, I think > you'll either be very happy (or very disappointed, seeing how much work > you put in to creating your own config files) to know that Zope 2.7+ > instances have their own configuration file which has a syntax patterned > after an Apache configuration file; the parsing system uses the ZConfig > package (http://www.zope.org/Members/fdrake/zconfig/). I have attached > the zope.conf.in file that represents a valid Zope instance > configuration file. I'm both disappointed and happy for the same reason :) When 2.7 will be out i'll adapt my zopectl to the new Zope installation procedure. > As an upshot, z2.py no longer exists and the "zopectl" that runs Zope [...] That's not big deal: I'll manage instance operation trough instance specific zopectl script. > I'd love to see your zopectl system work with Zope 2.7, and though I [...] > If you want it to support Zope 2.7, I'd be happy to answer any questions > about the new installation/startup process. I'll keep it a separate package, and i surely take advantage of your help. > In particular, I think you'd need to change your zopectl conf file. [...] I'll most probably do in this way. > Support for installing docs to a specific directory is no big deal. > I'll add it to the Zope 2.7 TODO. Sounds cool. > I'd advise against installing Zope library files into site-packages > unless you put them in a site-packages subdirectory (like > site-packages/zope270 or site-packages/zope271). I'll keep this in mind. > If you can provide specific direction on how to make the Zope source > tarball installer service your goals better, I'll be happy to try to > implement any suggestions given that it makes sense in the larger > cross-platform context. I'll mail you privately for this. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
Re: FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Thu, Jun 19, 2003 at 09:26:51AM +1000, Adrian van den Dries wrote: > Well, if you're going to have a policy shoot-out: [...] > I think most of us would agree that .py(c) files are *libraries* and > not *data files*. Data files would be the skeleton instance > directory. Of course i do not agree, and your vision of those documents is quite erroneous, but this is an off-topic issue so i won't discusse it here. ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
FHS, zopectl, #925, Re: [Zope-dev] 2.7 installation
On Wed, Jun 18, 2003 at 11:23:15AM -0400, Chris McDonough wrote: > Actually the scripts in $INSTANCE/bin aren't shell wrappers for things > in $PREFIX/bin, they're shell wrappers for thing in > $PREFIX/lib/python/Zope/Startup. But yes, they are shell wrappers. And so they would be copied for all instance installed: they would not probably be that large, but what about symbolik links? > If you made a global control script that worked as per your example, how > would you identify where the 'default' instance is? I was not aware of a zopectl in the repository so i builded one in python for Debian. As i can see it's quite more powerful than the one you are going to include: http://packages.debian.org/unstable/admin/zopectl.html I would care about any comment. > FWIW, I'd be very opposed to any sort of limitations on where instance > homes could be placed to service this global control script's need to > find instances. [...] > http://dev.zope.org/Wikis/DevSite/Proposals/InstallationAndConfiguration > dated Aug 22, 2002 8:09 pm for more background. It's my opinion that a zope instance can be described trough a configuration file, thus not requiring multiple commands or links but rather a single command capable of using multiple configuration files. If you combine my zopectl script with the patch is proposed for z2.py (http://collector.zope.org/Zope/925), you'll have a good FHS[1] compliant framework for multiple INSTANCE_HOMEs (being still able to place any file where you like). > This sounds good. I'm not so sure about $SKELPREFIX. Maybe we could [...] > libraries in the lib directory). This is why they're currently not > broken apart. To say it all there is only one thing i really need: a way to install _all_ documentation files under a separate directory in a way thay cannot overlap. For what concern Debian, the intallation home will still be /usr/lib/zope untill python fully comply FHS[1] (http://python.org/sf/588756). I'll probably move it to /usr/lib/python2.1/site-packages in future, but i'm still not sure. > In the past, my offers to provide upstream support for Debian packaging > hasn't been met with much enthusiasm. If I can make it easier for > people to package Zope for Debian, I'd love to, but I'd need to have > some buyin and support from the current Debian packagers. Otherwise, it > ends up being a waste of time on both of our parts as it won't be what's > best for either of us. It's not that easy to co-maintain the Debian package for Zope: we actually lacks the structures to set up work with non Debian Developers. I suppose this problem will be solved soon, but if you like i can start collecting patches for the CVS repository i've already set up for that purpose. Take a look at https://alioth.debian.org/projects/pkg-zope and its CVS repository. > Debian's packaging and installation strategy for Zope has always been > very customized and divergent from the Zope source distribution's > packaging and installation strategy. At very worst, it could stay this > way. Debian has choosed to be be strictly compliant to FHS[1], including it in the Debian Packaing Policy. Not complying to Debian Policy is considered a grave bug for any package in the distribution. Current Zope upstream package is not that compliant, so we always have to modify the package. I hope this will change in future. ciao, [1] http://www.pathname.com/fhs/ -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][A-Za-z\-]*[iy]'\?s$ | as fine or rude sentences have Luca, a wannabe ``Good guy''. | something in common: they local LANG="[EMAIL PROTECTED]" | don't depend on the language. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] Some gcc warnings building zope 2.6.1
Hi, I got these warnings building zope (you might be interested in fixing some/all of them): BTrees/BucketTemplate.c:214: warning: `bucket_append' defined but not used BTrees/BucketTemplate.c:214: warning: `bucket_append' defined but not used BTrees/BucketTemplate.c:214: warning: `bucket_append' defined but not used lib/python/Shared/DC/xml/pyexpat/expat/xmlparse/xmlparse.c:2341: warning: `errorProcessor' defined but not used In file included from lib/python/Shared/DC/xml/pyexpat/expat/xmltok/xmltok.c:260: lib/python/Shared/DC/xml/pyexpat/expat/xmltok/xmltok_impl.c: In function `normal_getAtts': lib/python/Shared/DC/xml/pyexpat/expat/xmltok/xmltok_impl.c:1394: warning: `open' might be used uninitialized in this function In file included from lib/python/Shared/DC/xml/pyexpat/expat/xmltok/xmltok.c:653: lib/python/Shared/DC/xml/pyexpat/expat/xmltok/xmltok_impl.c: In function `little2_getAtts': lib/python/Shared/DC/xml/pyexpat/expat/xmltok/xmltok_impl.c:1394: warning: `open' might be used uninitialized in this function In file included from lib/python/Shared/DC/xml/pyexpat/expat/xmltok/xmltok.c:792: lib/python/Shared/DC/xml/pyexpat/expat/xmltok/xmltok_impl.c: In function `big2_getAtts': lib/python/Shared/DC/xml/pyexpat/expat/xmltok/xmltok_impl.c:1394: warning: `open' might be used uninitialized in this function lib/python/Shared/DC/xml/pyexpat/expat/xmltok/xmltok.c: In function `initScan': lib/python/Shared/DC/xml/pyexpat/expat/xmltok/xmltok.c:1494: warning: subscript has type `char' lib/python/Shared/DC/xml/pyexpat/dcpyexpat.c: In function `my_StartElementHandler': lib/python/Shared/DC/xml/pyexpat/dcpyexpat.c:73: warning: `attrs_k' might be used uninitialized in this function lib/python/Shared/DC/xml/pyexpat/dcpyexpat.c: In function `initdcpyexpat': lib/python/Shared/DC/xml/pyexpat/dcpyexpat.c:718: warning: unused variable `rev' ciao, -- Luca - De Whiskey's - De Vitis | Elegant or ugly code as well aliases: Luca ^De [A-Z][-A-Za-z]*[iy]'?s$ | as fine or rude sentences have Infinite loop: see `Loop, infinite'.| something in common: they Loop, infinite: see `Infinite loop'.| don't depend on the language. ___ Zope-Dev maillist - [EMAIL PROTECTED] http://mail.zope.org/mailman/listinfo/zope-dev ** No cross posts or HTML encoding! ** (Related lists - http://mail.zope.org/mailman/listinfo/zope-announce http://mail.zope.org/mailman/listinfo/zope )
[Zope-dev] just 2 bits on stupid_clean
Hi,
to let the 'find' in stupid_clean remove even file names with spaces you may
replace it with:
find . -name '*.o' -o -name '*.so' -o -name '*.py[co]' -o -name 'core*' |
while read file
do rm -f "$file"
done
It's not clear to me why you put that command in a separate file, but the clean
target of the main Makefile could easily look like:
BUILDED_FILE=-name '*.o' -o -name '*.so' -o -name '*.py[co]' -o -name 'core*'
clean:
find . $(BUILDED_FILE) | \
while read file ;\
do rm -f "$file" ;\
done
rm -rf lib/python/build
I added last call to rm since no Makefile removes lib/python/build.
ciao,
--
Luca - De Whiskey's - De Vitis | Elegant or ugly code as well
aliases: Luca ^De [A-Z][-A-Za-z]*[iy]'?s$ | as fine or rude sentences have
Infinite loop: see `Loop, infinite'.| something in common: they
Loop, infinite: see `Infinite loop'.| don't depend on the language.
___
Zope-Dev maillist - [EMAIL PROTECTED]
http://mail.zope.org/mailman/listinfo/zope-dev
** No cross posts or HTML encoding! **
(Related lists -
http://mail.zope.org/mailman/listinfo/zope-announce
http://mail.zope.org/mailman/listinfo/zope )
