Re: Submission process for libtool?
Sam James <[email protected]>
| Newsgroups | gmane.comp.gnu.libtool.general |
|---|---|
| Message-ID | <[email protected]> |
> On 31 Mar 2022, at 21:42, Richard Purdie <[email protected]> wrote: > > Hi, > > It was great to see a libtool release, thanks for that! > > I upgraded Yocto Project to it in time for our LTS release: > > https://git.yoctoproject.org/poky/commit/?id=ff7b41573842a403c81f58bee41fc8163a9d7754 > > so far things seem reasonable, we've had a few minor issues but they're not > really libtool's fault or concern. One interesting quirk was that the shell > script optimisation changes made between 2.4.6 and 2.4.7 resulted in very long > (6,000+ character) pathnames being passed to the C library functions. This upset > our fakeroot emulation but we've fixed that to workaround the issue. > Nice and smooth so far as well here. > Yocto Project is carrying a few patches. I did clean them up and shared many of > them in October: > > https://lists.gnu.org/archive/html/libtool-patches/2021-10/msg00012.html > > Some are more important than others and there what I believe are good bug fixes > in there. My questions: > > a) Is there a possibility these could be considered for merging? > > [snip] > Thanks for asking this and am wondering the same thing. Hoping for your patches to get in (as Yocto's needs often align with ours) and then I plan on revisiting our (Gentoo's) stack. > Thanks, > Richard Best, sam
signature.asc
(application/pgp-signature, 618 B)
-----BEGIN PGP SIGNATURE----- iQGTBAEBCgB9FiEEYOpPv/uDUzOcqtTy9JIoEO6gSDsFAmJGU2JfFIAAAAAALgAo aXNzdWVyLWZwckBub3RhdGlvbnMub3BlbnBncC5maWZ0aGhvcnNlbWFuLm5ldDYw RUE0RkJGRkI4MzUzMzM5Q0FBRDRGMkY0OTIyODEwRUVBMDQ4M0IACgkQ9JIoEO6g SDtvQgf+MifXehG1vv2Odj5FcXTs4P3A2+jryZoNc5zlbr2eRZIWhSelAz9YI5th +ZSWciQvGqEPbE6CEG85bjCZX6ZtyqMu6iGsjZwbg9j2BbXUYWIH/ZmyTcVcBAaU 31cJsI1l5PQsRcYB6GdudqRDMZwcRvtfrc7p6Af20Z5eXvLeyRySu0iZq/Wd6E9w hVXOLxGihKvZ6MCP4js5Ka0FHM1BlBtbFGgOwicc4V2SMfKEent9QniTEwSiZLUX lhOnqW4SbXkXknFkdGaCS6i1MQo8mOkxNoYMV/n8gDzfjVpnAdS4nymQAShtN9Ki k10zULDeMPNgwrdD+KZB529joaJUYg== =7v8n -----END PGP SIGNATURE-----