Page MenuHomeSolus

Mesa Library - libosmesa
Closed, ResolvedPublic

Description

I am working on a package requested in T9832 and have found that a dependency is not available. Working on something like mesa is far beyond my skill set.

Packages: "Mesa Off-screen rendering extension"
libosmesa6
ibosmesa6-dev

mesa docs on off screen rendering
mesa builds docks regarding libraries

Related Objects

Event Timeline

But please note that that package request hasn't been accepted for inclusion yet. Maybe bump the task (since it has been sitting since July 28th), but don't submit your package diff before that.

Are you referring to the freedesktop tool? Apologies, I'm still learning.

But please note that that package request hasn't been accepted for inclusion yet. Maybe bump the task (since it has been sitting since July 28th), but don't submit your package diff before that.

Okay, I'm still trying to figure out how this all works. The contribution documentation isn't all that straight forward, and I just chose a package request that seemed easy to get started with.

Are you referring to the freedesktop tool? Apologies, I'm still learning.

If that's in response to Gavin Zhao's comment: He meant that you can use the line pkgconfig(osmesa) in the builddeps section of your package.yml to include the necessary dependency.

One can either use package names directly, or preferably these pkgconfig descriptors to specify dependencies (if available). You can search which package provides a certain pkgconfig with the script common/Scripts/epcsearch.py

Okay, I'm still trying to figure out how this all works. The contribution documentation isn't all that straight forward, and I just chose a package request that seemed easy to get started with.

No worries. If you look at the referenced package request (T9832), at the top left it says Open, Needs Triage. This means that no team member had a look at it to either accept or refuse inclusion of this app into the repository. In this particular case it seems like the request unfortunately went unnoticed altogether, so that's why I recommended a bump of the task. As soon as the status is set to Accepted for Inclusion for any package request, you're free to provide a patch to include that package.

@rrfss No worries! Here's my process of finding (guessing) what package it is:

  1. eopkg search libosmesa => nothing
  2. eopkg search osmesa => nothing
  3. eopkg search mesa, some results
  4. eopkg info mesalib-devel; not mesalib because the -devel packages containing development files are usually the ones needed.
  5. In the Provides: section, choose the one that seems to make the most sense to you.

There's probably a better way (e.g. using the script Staudey mentioned) but at least for me this can deal with most packages.

Thanks, guys! I'll have to read the packaging documentation more thoroughly to better understand the package file. I'll take note of that script for the future. I managed to get to 4 on your list @GZGavinZhao before opening this task, so at least I was on the right track.

If I watch through the tutorial videos on the Solus YouTube page and read the docs more carefully, I should be able to get something done. I figured getting my feet wet with packaging could be a good start. Really I'm interested in UI design for budgie, but I have a learning curve to beat.

... at the top left, it says Open, Needs Triage. This means that no team member had a look at it to either accept or refuse inclusion of this app into the repository. In this particular case it seems like the request unfortunately went unnoticed altogether, so that's why I recommended a bump of the task. As soon as the status is set to Accepted for Inclusion for any package request, you're free to provide a patch to include that package

Is this still the active repo for the help docs? I want to make an addition.

Also, I live on disability and have been looking for a project to do. I can dedicate a significant amount of time during the week towards Solus if it's needed; I'm just not a skilled programmer yet.

Is this still the active repo for the help docs? I want to make an addition.

Yup, that's the current Help Center Docs repo.

It takes everyone a few tries until they get everything right when it comes to packaging, so just keep at it ? (and if your addition can make life easier for new packagers, even better ? )

Staudey claimed this task.