Re: What is UpdateXorgRecipe? And how do I update Xorg-Server?
Philip White <[email protected]> Sat, 12 Jan 2019 00:33:14 -0500
| Newsgroups | gmane.linux.distributions.gobo.general |
|---|---|
| Message-ID | <CAMXcy6yEWx6QF9aVZczAx2_=As=AJ5KXGcSYD0LmifqCrnnWQg@mail.gmail.com> |
--===============3906153213743123682== Content-Type: multipart/alternative; boundary="0000000000006466c0057f3c26f3" --0000000000006466c0057f3c26f3 Content-Type: text/plain; charset="UTF-8" This is a pretty helpful response, but I just sat down to try working on this because I had some time and I'm running into issues making a recipe for Meson. First question: What is the right approach to "package management" in gobolinux? Intuitively, I'm thinking that everything should have a recipe, and if something is broken, the recipe should be fixed, or if something doesn't have a recipe but you want to install it, you should make a Recipe. Of course, the filesystem structure is such that you don't always need to have a recipe for something, but it would seem that having a recipe for everything would be better if someone is willing to put in the work. Specifically, if you are recommending that I install meson, why isn't there a recipe for it? Or, why do I have to fix Xorg myself? I'm not really complaining, I just would have expected it to have been done, so I'm thinking I could be misunderstanding gobolinux. Second question: How do I get this Recipe for Meson to work? # Recipe (MakeRecipe) for Meson by Philip White <[email protected]>, on Thu Jan 3 21:00:28 EST 2019 # Recipe for version 0.49.0 by Philip White <[email protected]>, on Thu Jan 3 21:00:28 EST 2019 compile_version=016.02 url="https://github.com/mesonbuild/meson/archive/0.49.0.tar.gz" file="meson-0.49.0.tar.gz" file_size=1911251 file_md5=a615fdb0d5920aa78175cda18a6f838f dir='meson-0.49.0' recipe_type=python python_major=3 The Recipe builds just fine, but `meson` is not a command on my path. I thought perhaps I should try to run `pip3 install meson` to do things the easy way, but apparently Pip is out of date (why is that); that hearkens back to the first question though. On Sat, Jan 5, 2019 at 8:21 PM Robert Alexander <[email protected]> wrote: > > When I ran `startx` on the next boot, the server shutdown > > because the VESA driver's ABI was at a different version than Xorg's. > > So I tried update that driver but I ran into some other issues. I > > could describe those issues, but I'm feeling like that isn't the > > root issue. > > I am not currently running GoboLinux but I remember ABI-related problems > and xorg-server not starting. > > What I usually do is to make sure that LLVM is up to date; and cmake; > then I compile meson ( > http://www.linuxfromscratch.org/lfs/view/systemd/chapter06/meson.html > ) (even though the URL includes systemd, meson works perfectly well > without systemd of course; I only have this "bookmarked" as link, > LFS/BLFS instructions can be super-helpful). After meson I tend to > compile the xorg-libs (libx11, libice, libsm, libxcb - all available > on the same URL where the xorg-server is), then I compile the > xorg-server. Here you have to be a bit careful in that I have had > problems in the past; e. g. wayland related parts aren't that good; > I tend to do things such as --disable-xwayland-eglstream and similar > to xorg-server. This serves me better than enabling these snippets. > > By the way, from my own experience it is quite hard to break a > GoboLinux system because you should always have the older versions > in the respective directory under /Programs/ so you can just > re-symlink that. :) > > To your problem like this: > > > Requested 'xproto >= 7.0.31' but version of Xproto is 7.0.29 > Requested 'randrproto >= 1.6.0' but version of RandrProto is 1.5.0 > Requested 'presentproto >= 1.1' but version of PresentProto is 1.0 > > > I think if you install > > https://www.x.org/releases/individual/proto/xorgproto-2018.4.tar.bz2 > > then this should be fine. > > That has all the .pc files as far as I can see for the protos: > > scrnsaverproto.pc, trapproto.pc, videoproto.pc and so forth. > > I also recommend to you to keep information in a text file - this > may help you at a later time a LOT. I started noting down how > to resolve some problems within the yaml-files that I use to > compile/install programs from source; a bit like the LFS/BLFS > project but more tuned towards the problems I encounter. > > I also used to autogenerate something similar to LFS/BLFS - will > try to see to do so and then make this available somewhere again. > > PS: The mailing interface confuses me too a bit. I see your emails > but I don't see the other email that came first in 2019 altogether, > so I could not hit on "reply" (I sent a mail to the email listed though). > > I find mailing lists pretty confusing altogether in general. > > On Sat, Jan 5, 2019 at 6:52 PM Philip White <[email protected]> > wrote: > >> I realized that digest mode is not what I want for a mailing list, since >> I cannot reply to emails individually. >> >> Anyway, my attempt to build i3 has been sidetracked because I ran >> >> InstallPackage Xorg-Server >> >> which broke X. When I ran `startx` on the next boot, the server shutdown >> because the VESA driver's ABI was at a different version than Xorg's. So I >> tried update that driver but I ran into some other issues. I could describe >> those issues, but I'm feeling like that isn't the root issue. >> >> I would expect this is an issue other people have run into, since nearly >> everyone uses Xorg, and people generally keep their systems up to the >> latest version. >> >> While looking for a solution, I noticed the UpdateXorgRecipe script. I >> ran it, and it made a bunch of local recipes, but as far as I can tell, it >> didn't actually compile anything. Thus, I tried to run `Compile >> Xorg-Server` to compile the newly generated recipes. I got the dependency >> issues: >> >> Requested 'xproto >= 7.0.31' but version of Xproto is 7.0.29 >> Requested 'randrproto >= 1.6.0' but version of RandrProto is 1.5.0 >> Requested 'presentproto >= 1.1' but version of PresentProto is 1.0 >> >> Has anybody encountered this error before? Also, is there any >> documentation for what UpdateXorgRecipe does? >> >> Last question, how do I search these mailing list archives? The link on >> the website points to >> http://search.gmane.org/search.php?group=gmane.linux.distributions.gobo.general, >> which does not work. >> >> Thanks, >> Philip >> _______________________________________________ >> gobolinux-users mailing list >> [email protected] >> http://lists.gobolinux.org/mailman/listinfo/gobolinux-users >> > _______________________________________________ > gobolinux-users mailing list > [email protected] > http://lists.gobolinux.org/mailman/listinfo/gobolinux-users > --0000000000006466c0057f3c26f3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div dir=3D"ltr"><div di= r=3D"ltr"><div>This is a pretty helpful response, but I just sat down to tr= y working on this because I had some time and I'm running into issues m= aking a recipe for Meson.</div><div><br></div><div>First question: What is = the right approach to "package management" in gobolinux?</div><di= v><br></div><div>Intuitively, I'm thinking that everything should have = a recipe, and if something is broken, the recipe should be fixed, or if som= ething doesn't have a recipe but you want to install it, you should mak= e a Recipe. Of course, the filesystem structure is such that you don't = always need to have a recipe for something, but it would seem that having a= recipe for everything would be better if someone is willing to put in the = work. Specifically, if you are recommending that I install meson, why isn&#= 39;t there a recipe for it? Or, why do I have to fix Xorg myself? I'm n= ot really complaining, I just would have expected it to have been done, so = I'm thinking I could be misunderstanding gobolinux.</div><div><br></div= ><div>Second question: How do I get this Recipe for Meson to work?</div><di= v><br></div><div># Recipe (MakeRecipe) for Meson by Philip White <<a hre= f=3D"mailto:[email protected]">[email protected]</a>>,= on Thu Jan 3 21:00:28 EST 2019<br># Recipe for version 0.49.0 by Philip Wh= ite <<a href=3D"mailto:[email protected]">philipwhite@cedarvill= e.edu</a>>, on Thu Jan 3 21:00:28 EST 2019<br>compile_version=3D016.02<b= r>url=3D"<a href=3D"https://github.com/mesonbuild/meson/archive/0.49.0= .tar.gz">https://github.com/mesonbuild/meson/archive/0.49.0.tar.gz</a>"= ;<br>file=3D"meson-0.49.0.tar.gz"<br>file_size=3D1911251<br>file_= md5=3Da615fdb0d5920aa78175cda18a6f838f<br>dir=3D'meson-0.49.0'<br>r= ecipe_type=3Dpython<br>python_major=3D3<br></div><div></div><div><br></div>= <div>The Recipe builds just fine, but `meson` is not a command on my path.<= /div><div><br></div><div>I thought perhaps I should try to run `pip3 instal= l meson` to do things the easy way, but apparently Pip is out of date (why = is that); that hearkens back to the first question though.<br></div></div><= br><div class=3D"gmail_quote"><div dir=3D"ltr">On Sat, Jan 5, 2019 at 8:21 = PM Robert Alexander <<a href=3D"mailto:[email protected]">shevegen@gmai= l.com</a>> wrote:<br></div><blockquote class=3D"gmail_quote" style=3D"ma= rgin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:= 1ex"><div dir=3D"ltr"><div dir=3D"ltr">> When I ran `startx` on the next= boot, the server shutdown<br>> because the VESA driver's ABI was at= a different version than Xorg's.<br>> So I tried update that driver= but I ran into some other issues. I<br>> could describe those issues, b= ut I'm feeling like that isn't the<br>> root issue.<br><br>I am = not currently running GoboLinux but I remember ABI-related problems<br>and = xorg-server not starting.<br><br>What I usually do is to make sure that LLV= M is up to date; and cmake;<br>then I compile meson (<br>=C2=A0 <a href=3D"= http://www.linuxfromscratch.org/lfs/view/systemd/chapter06/meson.html" targ= et=3D"_blank">http://www.linuxfromscratch.org/lfs/view/systemd/chapter06/me= son.html</a><br>) (even though the URL includes systemd, meson works perfec= tly well <br>without systemd of course; I only have this "bookmarked&q= uot; as link,<br>LFS/BLFS instructions can be super-helpful). After meson I= tend to<br>compile the xorg-libs (libx11, libice, libsm, libxcb - all avai= lable<br>on the same URL where the xorg-server is), then I compile the<br>x= org-server. Here you have to be a bit careful in that I have had<br>problem= s in the past; e. g. wayland related parts aren't that good;<br>I tend = to do things such as --disable-xwayland-eglstream and similar<br>to xorg-se= rver. This serves me better than enabling these snippets.<br><br>By the way= , from my own experience it is quite hard to break a<br>GoboLinux system be= cause you should always have the older versions<br>in the respective direct= ory under /Programs/ so you can just <br>re-symlink that. :)<br><br>To your= problem like this:<br><br><br>Requested 'xproto >=3D 7.0.31' bu= t version of Xproto is 7.0.29<br>Requested 'randrproto >=3D 1.6.0= 9; but version of RandrProto is 1.5.0<br>Requested 'presentproto >= =3D 1.1' but version of PresentProto is 1.0<br><br><br>I think if you i= nstall <br><br><a href=3D"https://www.x.org/releases/individual/proto/xorgp= roto-2018.4.tar.bz2" target=3D"_blank">https://www.x.org/releases/individua= l/proto/xorgproto-2018.4.tar.bz2</a><br><br>then this should be fine.<br><b= r>That has all the .pc files as far as I can see for the protos:<br><br>scr= nsaverproto.pc, trapproto.pc, videoproto.pc and so forth.<br><br>I also rec= ommend to you to keep information in a text file - this<br>may help you at = a later time a LOT. I started noting down how<br>to resolve some problems w= ithin the yaml-files that I use to <br>compile/install programs from source= ; a bit like the LFS/BLFS<br>project but more tuned towards the problems I = encounter.<br><br>I also used to autogenerate something similar to LFS/BLFS= - will<br>try to see to do so and then make this available somewhere again= .</div><div dir=3D"ltr"><br></div><div>PS: The mailing interface confuses m= e too a bit. I see your emails</div><div>but I don't see the other emai= l that came first in 2019 altogether,</div><div>so I could not hit on "= ;reply" (I sent a mail to the email listed though).</div><div><br></di= v><div>I find mailing lists pretty confusing altogether in general.<br></di= v></div><br><div class=3D"gmail_quote"><div dir=3D"ltr">On Sat, Jan 5, 2019= at 6:52 PM Philip White <<a href=3D"mailto:[email protected]" = target=3D"_blank">[email protected]</a>> wrote:<br></div><block= quote class=3D"gmail_quote" style=3D"margin:0px 0px 0px 0.8ex;border-left:1= px solid rgb(204,204,204);padding-left:1ex"><div dir=3D"ltr"><div dir=3D"lt= r"><div>I realized that digest mode is not what I want for a mailing list, = since I cannot reply to emails individually.</div><div><br></div><div>Anywa= y, my attempt to build i3 has been sidetracked because I ran</div><div><br>= </div><div>InstallPackage Xorg-Server</div><div><br></div><div>which broke = X. When I ran `startx` on the next boot, the server shutdown because the VE= SA driver's ABI was at a different version than Xorg's. So I tried = update that driver but I ran into some other issues. I could describe those= issues, but I'm feeling like that isn't the root issue.</div><div>= <br></div><div>I would expect this is an issue other people have run into, = since nearly everyone uses Xorg, and people generally keep their systems up= to the latest version.</div><div><br></div><div>While looking for a soluti= on, I noticed the UpdateXorgRecipe script. I ran it, and it made a bunch of= local recipes, but as far as I can tell, it didn't actually compile an= ything. Thus, I tried to run `Compile Xorg-Server` to compile the newly gen= erated recipes. I got the dependency issues:</div><div><br></div><div>Reque= sted 'xproto >=3D 7.0.31' but version of Xproto is 7.0.29<br><di= v>Requested 'randrproto >=3D 1.6.0' but version of RandrProto is= 1.5.0<br><div>Requested 'presentproto >=3D 1.1' but version of = PresentProto is 1.0</div><div><br></div><div>Has anybody encountered this e= rror before? Also, is there any documentation for what UpdateXorgRecipe doe= s?</div><div><br></div><div>Last question, how do I search these mailing li= st archives? The link on the website points to <a href=3D"http://search.gma= ne.org/search.php?group=3Dgmane.linux.distributions.gobo.general" target=3D= "_blank">http://search.gmane.org/search.php?group=3Dgmane.linux.distributio= ns.gobo.general</a>, which does not work.</div><div><br></div><div>Thanks,<= /div><div>Philip<br></div></div></div></div></div> _______________________________________________<br> gobolinux-users mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">go= [email protected]</a><br> <a href=3D"http://lists.gobolinux.org/mailman/listinfo/gobolinux-users" rel= =3D"noreferrer" target=3D"_blank">http://lists.gobolinux.org/mailman/listin= fo/gobolinux-users</a><br> </blockquote></div> _______________________________________________<br> gobolinux-users mailing list<br> <a href=3D"mailto:[email protected]" target=3D"_blank">go= [email protected]</a><br> <a href=3D"http://lists.gobolinux.org/mailman/listinfo/gobolinux-users" rel= =3D"noreferrer" target=3D"_blank">http://lists.gobolinux.org/mailman/listin= fo/gobolinux-users</a><br> </blockquote></div></div></div></div></div> --0000000000006466c0057f3c26f3-- --===============3906153213743123682== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: base64 Content-Disposition: inline X19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX19fX18KZ29ib2xpbnV4 LXVzZXJzIG1haWxpbmcgbGlzdApnb2JvbGludXgtdXNlcnNAbGlzdHMuZ29ib2xpbnV4Lm9yZwpo dHRwOi8vbGlzdHMuZ29ib2xpbnV4Lm9yZy9tYWlsbWFuL2xpc3RpbmZvL2dvYm9saW51eC11c2Vy cwo= --===============3906153213743123682==--