oship-dev team mailing list archive

[Tim Cook <timothywayne.cook@xxxxxxxxx>]

Hi guys,

Happy to see this discussion going on here.  I'm not going to get too
involved in this but I do (as always) have an opinion. ;-)

I think going the egg route is the eventual best option....but we have
to think about certain issues that we are kind of cheating around right
now.  We are currently embedding Pyparsing and PyCLIPS/CLIPS in order to
be certain that we get the Python 2.5 versions that work correctly.  I
guess this can be done in setup.py but we'll also need to edit the
PyCLIPS setup.py so that it behaves correctly since it wants to download
the CLIPS source into the current working directory and install it there
which doesn't work if we let Martian do it during the normal source scan
that it does under Grok.  

We can also eliminate some install steps if you guys can discover what
Plone4 (maybe other versions too?) and z3extnet is doing.  They create
the python2.5 virtual environment on the fly during installation.  I
think that is very cool but I haven't had time to examine how they do
that.

Cheers,
Tim


On Tue, 2009-09-29 at 10:16 -0300, Roberto Siqueira wrote:
> Hi, Maxwell:
>   I indeed have some considerations to add to this discussion. Firstly, 
> concerning the Mac install, please have a look at my initial attempts 
> here: https://lists.launchpad.net/oship-dev/msg00279.html . Those 
> attempts highlight the important question of having a good "packaging 
> system", if one wishes to simplify the installation process. In fact (as 
> of today), to be able to develop OSHIP we need all the following:
> 
> - a C compiling environment ("build-essential" in Ubuntu, 
> "slitaz-toolchain" in Slitaz, "XCode" in MacOSX etc);
> - the packaging system discussed above (apt-get/yum/tazpkg etc for 
> Linux, fink/macports for MacOSX etc);
> - the Bazaar version control system ("bazaar" package, wherever available);
> - a Python development environment ("python" and "python-dev" packages);
> - Python's easy_install ("setuptools" package);
> - Python's virtual environment ("virtualenv" package, or got though: 
> "easy_install virtualenv");
> - Python's Grok (right now supplied with the OSHIP code, but in 
> principle an independent "dependency");
> - the OSHIP code itself (got through the "bzr branch lp:oship" or "bzr 
> co lp:oship" commands).
> 
>   One solution is to pack all that in one big "blob", for every 
> platform. Actually, one can think of the Slitaz portable environment 
> I've just described as an example of this "maximalist" approach, to 
> install OSHIP (in fact, it's dead simple to create a custom ISO from it, 
> simply using the "tazlito" command: 
> http://www.slitaz.org/en/doc/handbook/gen-livecd.html). But let's note, 
> in passing, that this procedure has the advantage of already being 
> multiplatform (there are QEMU versions for Windows, MacOSX, Linux etc). 
> When this is not the case, many platform-specific "blobs" have to be 
> recreated for every new release, representing much more work for the 
> "blobbers" (like you and me).
> 
>   On the opposite side, we have the "minimalist" approaches. They may 
> simply take advantage of the different packaging systems (e.g. a .deb 
> for apt-get/Ubuntu or a .rpm for yum/Fedora -- a good one is still 
> missing for Windows, though) or, going a step further, also use the 
> Python installing mechanisms themselves (distutils, setuptools, PyPI 
> repository etc). My own personal opinion is  that, as we are now 
> approaching the 1.0 mark, using PyPI is the best solution for an easy, 
> multiplatform release/install: 
> http://grok.zope.org/documentation/how-to/releasing-software . [Putting 
> Grok as a separate dependency also deserves to be further explored -- 
> this would make our OSHIP "egg" much smaller /portable.]
> 
>   HTH,
> Roberto.
> 
> Maxwell Dayvson a écrit :
> > Hi Roberto and all,
> > The Slitaz is cool. I'm talk with Tim about  an one click install for 
> > OSHIP. 
> > Would basically create a Debian and RPM package and a dmg for Mac.
> > I'm believe that in the near future will be very interesting to the 
> > distribution of Oship
> > What do you think?
> >
> > cheers
> >
> > 2009/9/28 Roberto Siqueira <siqueira@xxxxxxxxxxxxxxx 
> > <mailto:siqueira@xxxxxxxxxxxxxxx>>
> >
> >     Hi all,
> >      Due to my own "mobility" (so to speak) needs I've recently set up
> >     a portable OSHIP development environment, based on the amazingly
> >     small distro: Slitaz GNU/Linux
> >     (http://www.slitaz.org/en/index.html). As this technique may be
> >     useful for others developers as well, I decided to share this
> >     experience here.
> >
> >     [...]
> >
> >
> 
> _______________________________________________
> Mailing list: https://launchpad.net/~oship-dev
> Post to     : oship-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~oship-dev
> More help   : https://help.launchpad.net/ListHelp
-- 
***************************************************************
Timothy Cook, MSc

LinkedIn Profile:http://www.linkedin.com/in/timothywaynecook 
Skype ID == (upon request)
Academic.Edu Profile: http://uff.academia.edu/TimothyCook

You may get my Public GPG key from  popular keyservers or    
from this link http://timothywayne.cook.googlepages.com/home

Attachment: signature.asc
Description: This is a digitally signed message part