| 1 |
Samuel Holland wrote: |
| 2 |
> Hello, |
| 3 |
> |
| 4 |
> Over the past few months I have set up both a desktop and server system |
| 5 |
> with Gentoo Hardened Musl. In the course of doing so, I have accumulated |
| 6 |
> several patches (41 so far) and a couple of modified ebuilds. What is |
| 7 |
> the recommended thing to do with them? Should I open bugs for the FTBFS? |
| 8 |
> Should I prepare patches for adding to the musl overlay? Or should I |
| 9 |
> first try to get these changes upstream? |
| 10 |
|
| 11 |
In an ideal world, there is an active upstream, you send the patch |
| 12 |
upstream, it soon gets accepted, you open a bug with the backported |
| 13 |
upstream patch and the corresponding gentoo developer adds it to the |
| 14 |
tree. |
| 15 |
|
| 16 |
More realistically, it takes a while to get things upstream. It might |
| 17 |
also take some while to get the patches into good shape for upstream. |
| 18 |
So, I guess that in most cases a bug for each package is the most |
| 19 |
appropropriate (although it takes a lot of work), so that the |
| 20 |
upstream/in tree/in overlay status of the patch(es) can be kept track |
| 21 |
of. (For active packages likely used by only very few people, I would |
| 22 |
just go upstream, though.) |
| 23 |
|
| 24 |
> I can upload the patches to GitHub or somewhere (or post them here) if |
| 25 |
> that would be helpful. Some of them are quick patches (that might break |
| 26 |
> glibc, though I can test that); others are more thorough. |
| 27 |
|
| 28 |
This might be the easiest approach for you to make your patches |
| 29 |
available. Notice that there are already some patch collections |
| 30 |
(https://github.com/search?q=gentoo%20musl). |
| 31 |
|
| 32 |
> I would like to participate more in the Gentoo Musl and related projects |
| 33 |
> (side note: possibly as a GSoC student), but I am not sure the best way |
| 34 |
> to get involved. |
| 35 |
|
| 36 |
Helping with porting packages or solving bugs is surely a good way |
| 37 |
to get involved. |
| 38 |
|
| 39 |
> Also, for packages that I cannot get to compile or run, is it |
| 40 |
> appropriate to file a bug on b.g.o (since musl is experimental)? |
| 41 |
|
| 42 |
Yes, very much. There already is a not so small list of such bugs. |
| 43 |
(Just search for musl or look at the tracker |
| 44 |
https://bugs.gentoo.org/show_bug.cgi?id=430702 .) |
| 45 |
|
| 46 |
Thanks for offering your help! |
| 47 |
|
| 48 |
Felix |
| 49 |
|
| 50 |
PS: This list is very quiet. |
Archives