The setup.py isn't a distutils setup - all it basically has is....
os.system('g++ -c builtin_.cpp sets_.cpp random_.cpp math_.cpp copy_.cpp
sys_.cpp')
if sys.platform == 'darwin':
os.system('libtool -static builtin_.o copy_.o math_.o random_.o sets_.o
sys_.o -o libss.a; ranlib libss.a')
else:
os.system('ld -Ur -o libss.a builtin_.o sets_.o random_.o math_.o copy_.o
sys_.o')
(all intermixed with a bunch of "if sys.platform == 'X':")
Plus the script builds a launch executable, but uses the CWD so I just broke
out the couple of relevant lines into the PKGBUILD instead of patching the
setup.py into something usable.
I have to keep the C++ source files because they are needed to compile any
python program that you shedskin to C++. And shedskin expects to find them in
the same dir as the binary (or rather the Makefile that shedskin generates
does.).
So I am back to my original question.... Where is the right place to put
these kind of *apps* (I actually have a couple like this.)
Looking at one of the other apps - pears - Gentoo and the spec file do have it
setup to install to the site-packages dir so maybe that is *proper*
I am so confused..... lol
--Todd
On Thursday 29 September 2005 01:31 pm, Aaron Griffin wrote:
> On 9/29/05, Todd Maynard <[EMAIL PROTECTED]> wrote:
> > This definitely feels like an abuse of /opt/ but I don't think that
> > splitting this up all over the place is going to work either. I have
> > 99.44% convinced myself that /usr/share/$pkgname is appropriate with a
> > scipt in /usr/bin that calls the executable under /usr/share/
>
> You shouldn't distribute the c++ code. Don't copy over the .hpp and
> .cpp files (or the .o). You also shouldn't need the setup.py file,
> which maybe you should use (as it looks like it has a distutils
> functionality) - "python setup.py install --root=/usr" ??
>
> > [EMAIL PROTECTED] ~]$ pacman -Ql shedskin
> > shedskin /opt/
> > shedskin /opt/shedskin/
> > shedskin /opt/shedskin/LICENSE
> > shedskin /opt/shedskin/README
> > shedskin /opt/shedskin/bert.py
> > shedskin /opt/shedskin/builtin_.py
> > shedskin /opt/shedskin/copy_.py
> > shedskin /opt/shedskin/hoppa
> > shedskin /opt/shedskin/libss.a
> > shedskin /opt/shedskin/math_.py
> > shedskin /opt/shedskin/random_.py
> > shedskin /opt/shedskin/sets_.py
> > shedskin /opt/shedskin/ss.py
> > shedskin /opt/shedskin/sys_.py
> > shedskin /opt/shedskin/test.py
> > shedskin /opt/shedskin/unit.py
> > shedskin /opt/shedskin/uuf250-010.cnf
> > shedskin /usr/
> > shedskin /usr/bin/
> > shedskin /usr/bin/ss
> >
> > On Wednesday 28 September 2005 11:24 am, Aaron Griffin wrote:
> > > On 9/28/05, Andrew Conkling <[EMAIL PROTECTED]> wrote:
> > > > You should probably be installing the python scripts to
> > > > site-packages, e.g. via distutils. That's the right place for Python
> > > > stuff, but I'm not sure about the rest.
> > > >
> > > > http://www.python.org/sigs/distutils-sig/doc/
> > >
> > > That's not nessecarilly true - site-packages is for python _modules_.
> > > If it is a series of stand-alone applications they do not belong in
> > > site-packages.
> > >
> > > > On 9/28/05, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote:
> > > > > What is the *right* place to install an application that is
> > > > > basically just a directory full of python scripts and such... An
> > > > > example app would be shedskin
> > > > > http://aur.archlinux.org/packages.php?do_Details=1&ID=2254 .
> > >
> > > Hmmm, I don't have time to build and look into it - can you give me
> > > the filelist from makepkg (just email the text, it can't be that
> > > much). For the most part, everything should be under /usr, with
> > > binaries in bin and data in share/<pkgname> - I'd like to see a list
> > > of what you're installing to better diagnose.
> > >
> > > > > I am currently dumping the whole thing into /opt/$pkgname but it
> > > > > seems like an abuse of /opt. Would /usr/share/$pkgname be better?
> > > > > Or is somewhere else more appropriate?
> > >
> > > I personally feel /opt is overused. /opt, to me, is for very large
> > > piles of related stuff. kde, gnome, and the mozilla suite should go
> > > there, but something like bittorrent (which was in /opt a while back)
> > > doesn't belong there - it's only 3 or 4 executables and some python
> > > site-packages.
> > >
> > > - phrak -
> > >
> > > _______________________________________________
> > > arch mailing list
> > > [email protected]
> > > http://www.archlinux.org/mailman/listinfo/arch
_______________________________________________
arch mailing list
[email protected]
http://www.archlinux.org/mailman/listinfo/arch
