On Sep 24, 2003, at 15:28, Marc Recht  was heard saying:

> > The problem with Python is that it behaves differently on Darwin and
> > MacOS X (the MacOS version builds Carbon stuff)... Besides, it won't
> > build a shared library, only a Python framework.
>
> ?? Do you mean it doesn't build libpython* at all ? This could be handled
> with the PLIST.

It doesn't. libpython is supposed to be replaced with Python.framework
(Frameworks are the MacOS name for libraries-bundled-with-headers).

> > I'm moving this to tech-pkg because I need advice:
> > - do we wan't Python to build MacOS-specific stuff ?
>
> Why not? But IMHO this should be an extra pkg. (Like Michal proposed, eg.
> py-carbon)

Ok. I'll investigate on this -- I'm not sure if the Python build will let me
do so.

>
> > - do we really want a Python lib and/or a Python.framework (which needs
> > to be installed in a specific location, where it'll possibly conflict
> > with something else) ?
>
> I know next to nothing about Darwin/OSX, but maybe we could use a similiar
> approach to xpgwedge/x11-links for OSX ?

The problem is that frameworks have to be in specific locations, unless you
want all your non-Unix-friendly users to add a DYLD_FRAMEWORK_PATH variable in
hidden config files.

See you,
-- 
Julien T. Letessier                      http://www.mezis.net/
NetBSD developer - Packages collection   http://www.pkgsrc.org/
Solarpack Project member                 http://solarpack.sourceforge.net/

()  ascii ribbon campaign - against html mail & vCards
/\                        - against microsoft attachments

Key fingerprint = F1A3 C564 09FE 07A6 0327  7474 0F9F 5594 F657 9673