Mailinglist Archive: opensuse-packaging (155 mails)

< Previous Next >
Re: [opensuse-packaging] Adding a new package which depends on others
  • From: Greg Freemyer <greg.freemyer@xxxxxxxxx>
  • Date: Thu, 30 Jan 2014 14:11:03 -0500
  • Message-id: <CAGpXXZKBouTt5tpM531_G--qZE_J63ze1K9t_J-M0=+a3_uv-Q@mail.gmail.com>
On Thu, Jan 30, 2014 at 11:45 AM, Jan Engelhardt <jengelh@xxxxxxx> wrote:
On Wednesday 2014-01-29 16:08, Guillaume Gardet wrote:

I would like to add a new package (pocl) which depends on non-standard
packages :
* hwloc-devel which is in Factory and developped at devel:libraries:c_c++
* ocl-icd-devel which is in Education
* opencl-headers which is in Education
* uthash which is in devel:libraries:c_c++

I think devel:libraries:c_c++ or devel:tools projects may be fine for pocl
package. Is there anything better?

I hear OpenCL in context of science a lot (so "science" project), but
I do not eliminate the possibility that some other programs, such as
of the areas gaming and field-specific software (the kind that
Applications:Geo, /graphics/librecad is) might offer to use it as
well if present.

In the end, it does not matter what develprj it lives in as
long as everything comes together in Factory.

It looks like that is the problem. 3 of the dependencies are not in
Factory, they are instead in Education and/or devel:libraries:c_c++.

Assuming, there is no desire to push OpenCL to factory, then
I believe the best 4 options are:

Option 1:
Use Education as the devel project for OpenCL, and push uthash to factory

Option 2:
Use Education as the devel project for OpenCL, then create linked
packages in Education for devel:libraries:c_c++:uthash

Option 3:
Use Education as the devel project for OpenCL, then get
devel:libraries:c_c++ added to the metadata of the entire Education
project as a repo to search during builds.

As an example, if you look in the Education metadata
<https://build.opensuse.org/project/meta/Education> you see factory
builds in that repo already search devel:languages:perl and
devel:languages:python, so adding devel:libraries:c_c++ makes sense to
me.

====
<repository name="openSUSE_Factory">
<path project="openSUSE:Factory:NonFree" repository="standard"/>
<path project="openSUSE:Factory" repository="snapshot"/>
<path project="devel:languages:perl" repository="openSUSE_Factory"/>
<path project="devel:languages:python" repository="openSUSE_Factory"/>
<arch>i586</arch>
<arch>x86_64</arch>
</repository>
===

Option 4:
Use the Science project as the devel project and then link in all 3 of
the above needed projects that aren't in factory. I rule out adding
Education and c_c++ to Science as places to search only because the
Science project doesn't have any pre-existing extra repos to search
<https://build.opensuse.org/project/meta/science>

===
<repository name="openSUSE_Factory">
<path project="openSUSE:Factory:NonFree" repository="standard"/>
<path project="openSUSE:Factory" repository="snapshot"/>
<arch>x86_64</arch>
<arch>i586</arch>
</repository>
===

----------- conclusion -------------
Anyone willing to maintain uthash can ask for maintainer privileges
for that one package and push it to factory. Options 2 and 3 can only
be done by a Education Project maintainer. Option 4 requires a
Science Project maintainer.

Guillaume, hopefully that answers the generic question. If you want
to pursue options 2, 3 or 4, you need to reach out to the
Education/Science maintainers. Either directly or via this mailing
list (but with a new subject to get their attention.)

HTH
Greg
--
Greg Freemyer
--
To unsubscribe, e-mail: opensuse-packaging+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: opensuse-packaging+owner@xxxxxxxxxxxx

< Previous Next >