Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Follow Wine's libdir structure #158

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Follow Wine's libdir structure #158

wants to merge 2 commits into from

Conversation

9ary
Copy link
Contributor

@9ary 9ary commented Apr 12, 2023

Continuation of #154. I really would like for this to be merged in some form, so input on what direction to take it would be very valuable.

Not only is this friendlier to packagers, but it enables usage via
WINEDLLPATH.

Fixes iXit#123
winetricks can download future releases that it doesn't package yet.

Because it doesn't use our install script, we need to preserve the
existing structure in our release archive.

Let's just link the files back to the right place until downstreams
catch up.
@dhewg
Copy link
Collaborator

dhewg commented Apr 14, 2023

Time is sparse, I'll poke at it next week to see if a build time switch looks a bit nicer!

@EliasTheGrandMasterOfMistakes

this will be merged a day???
or gallium nine standalone is abandoned ?

@9ary
Copy link
Contributor Author

9ary commented Nov 13, 2023

I don't know, but I'm personally not interested in working on these patches anymore. If anyone wants to pick this up, as well as #155, and move things forward, they're welcome to.

That said, this PR in particular makes no functional changes, it's only to make life easier for distro maintainers. This repo is only a thin wrapper around the d3d9 implementation in mesa, which is maintained. There's little that ever needs to change in here, other than adapting to breaking changes in wine (the upcoming wayland support is one such change; gallium nine will continue to work, but only on X11 or xwayland as is currently the case).
A project being inactive does not mean it should be considered dead or abandoned.

@EliasTheGrandMasterOfMistakes

I don't know, but I'm personally not interested in working on these patches anymore. If anyone wants to pick this up, as well as #155, and move things forward, they're welcome to.

That said, this PR in particular makes no functional changes, it's only to make life easier for distro maintainers. This repo is only a thin wrapper around the d3d9 implementation in mesa, which is maintained. There's little that ever needs to change in here, other than adapting to breaking changes in wine (the upcoming wayland support is one such change; gallium nine will continue to work, but only on X11 or xwayland as is currently the case). A project being inactive does not mean it should be considered dead or abandoned.

thanks, sorry for my confusion.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants