search

stevendanna / habitat-plans

1 stars 2 forks source link

Finish xorg packaging #5

Open stevendanna opened 6 years ago

stevendanna commented 6 years ago

The following packages are listed as "Core X11 runtime " and "Core X11 build/development/install". See

https://www.x.org/wiki/ModuleDescriptions/

For each, we should either package it or decide we don't need to:

Libs and Proto

Apps

Data

Other stuff

baggerspion commented 6 years ago

At the very least, R requires:

stevendanna commented 6 years ago

I think the plan right now is to just focus on the deps of R rather than the whole list. We can go incrementally from there.

thommay commented 6 years ago

@fooishbar we're thinking about packing xorg libs and such for habitat (https://habitat.sh) - do you have feelings about the list above in terms of usefulness?

fooishbar commented 6 years ago

The @therealpadams list is definitely a good starting point; you'll also need xcb-proto to go with lib/xcb.

I have no idea what R uses, but I'd imagine the set of proto and lib packages would explode a fair bit if it's doing actual rendering. At the very minimum, you'll want proto/xextproto and lib/libXext to get SHM support, plus bigreqsproto. Assuming you're going to need to bring up a server somewhere, you'll end up pulling in the vast majority of proto/* (at least damage, composite, fixes, fonts and probably libXfont too, input, kb, panoramix, randr, render, etc etc) to build Xvfb as a headless render-and-capture server.

pthread-stubs should only be required for BSD, so if you can forget about that then I'd recommend that.

You'll also need app/xauth, app/xkbcomp and xkeyboard-config to bring up the server; having xdpyinfo and xwininfo is also going to be really useful.

Sorry, we really did get a bit carried away doing the module split. :\

stevendanna commented 6 years ago

@fooishbar Thank you for the helpful reply!

fooishbar commented 6 years ago

@stevendanna No problem. Happy to go through more, or I'm on IRC as daniels on Freenode if you need anything.

rsertelon commented 6 years ago

This is a nice tracking issue ;) Do you want to update it and keep track of work here, or should we do this over at core-plans?

stevendanna commented 6 years ago

@rsertelon Since we have most of these in core-plans now, let's do it over in core plans. My "plan subject to change" is to take a swing at getting the server compiled enough to run some of the test applications this weekend and make a list using that experience and the helpful comment above.