Fellow packagers,
after some discussions in our team, we figured that it would be neat if we could
build python modules for Python 2 and 3 from a single spec file. Now that a
great deal of python modules work with both pythons, this makes a lot of sense.
A good deal of work can be done by RPM macros. Then we could even seamlessly
start building modules for PyPy, Jython and other pythons.
A sample specfile, and the corresponding set of RPM macros, is attached. As you
can see, the appropriate subpackage is generated automatically by
%python_subpackages, build and install steps are handled through %python_build
and %python_install respectively. There is some more magic involved, as well as
possibilities for customization.
There is a minor problem with BuildRequires. As long as you only need
python-devel, it's not too bad to just list $flavor-devel requirements by hand.
It's worse when you require more subpackages, because then you need all of them
in both python2 and python3 versions.
It would be nice to be able to specify %{python_require Mako} and expand that to
all the necessary BuildRequires, but OBS blocks us here, because the limited
environment will not expand such macros.
mls, ro, or anyone from the OBS team, would it be possible to solve this?
Still, it basically doesn't matter if you list all the BuildRequires twice in
one spec or in two specs, so there.
Another thing I'm still unclear on are the filelists. It's certainly possible to
make a generic filelist, something along the lines of:
%package -n %flavor-%modname # python3-Mako
%defattr(-, root, root)
%{%flavor_sitelib}/*
%{%flavor_sitearch}/*
but this doesn't solve docs and possible other files.
Again, obviously, we can write the filelists by hand. But if you have good
suggestions for some smart macros here, I'd love to see them.
What do you folks think? Comments, questions?
m.
Hi all,
Google Summer of Code has kicked off, and we are in the process of
prepping for it. If you have a great idea, which could be done by a
Google Summer of Code student, and mentored by openSUSE, please add it
to our ideas page:
https://en.opensuse.org/openSUSE:GSOC_ideas
If possible, please spread the word to other relevant mailing lists!!!
--
Regards
Manu Gupta
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hi, My name is Dinara. Profiles:2014754. http://captero.zgr.name/
I would describe myself as a romantic, warm, honest woman. I like to have fun and if I smile or do something it is always from heart!
As probably every woman, I like cooking, making my house welcoming and comfortable.
I need a person, who will be my whole world, who is reliable, unattached. If you have really big heart and good sense of humor- you are exactly the man from my dreams!
Bye, Dinara.
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
While starting to look at libpng* issues I noticed that 'osc co -u
grahpics' gave an empty libpng12. For some reason
https://build.opensuse.org/package/show/openSUSE:Factory/libpng12 shows
that the package is developed at grahpics. But graphics/libpng12 has
just a _link to Factory and now a new project.diff.
I wonder how that happend?
Is graphics/libpng12 not the devel project for openSUSE:Factory/libpng12?
Olaf
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org
Hallo,
the autocheck script for factory has declined some packages I
accidentally auto-forwarded to factory.
What does the following decline message mean?
"Attention, oldchanges is not mentioned in spec files as source or patch."
How to fix this?
--
Ralf Lang
Linux Consultant / Developer
Tel.: +49-170-6381563
Mail: lang(a)b1-systems.de
B1 Systems GmbH
Osterfeldstraße 7 / 85088 Vohburg / http://www.b1-systems.de
GF: Ralph Dehner / Unternehmenssitz: Vohburg / AG: Ingolstadt,HRB 3537
Dear openSUSE contributor.
I'm contacting you personally, as an openSUSE Board member.
You certainly already know that we want to have a kicking openSUSE conference next 1st-4th May 2015 at the Haag (NL).
Thus I've found that creating special workshop organized by development project could foster our beloved distribution.
Please consult and share the following article
https://lizards.opensuse.org/?p=11193
I'm looking forward to see you at oSC!
--
Bruno Friedmann (tigerfoot)
openSUSE Member & Board, fsfe fellowship
GPG KEY : D5C9B751C4653227
irc: tigerfoot
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-packaging+owner(a)opensuse.org