| Message ID | 20230209163744.28973-5-maxim.cournoyer@gmail.com |
|---|---|
| State | New |
| Headers | show |
| Series | Improvements to Icedove (icons, gexps, un-bundling) | expand |
Hello,
Maxim Cournoyer <maxim.cournoyer@gmail.com> writes:
> - nspr-4.32
I'm not sure if I'm missing something but as far as I can tell you added
nspr-next, then never used it, and also removed nspr-4.32 from the
inputs here. Did you (or I) miss a nspr-next somewhere?
Morgan
Hi, Morgan Smith <Morgan.J.Smith@outlook.com> writes: > Hello, > > Maxim Cournoyer <maxim.cournoyer@gmail.com> writes: >> - nspr-4.32 > > I'm not sure if I'm missing something but as far as I can tell you added > nspr-next, then never used it, and also removed nspr-4.32 from the > inputs here. Did you (or I) miss a nspr-next somewhere? nspr is now propagated by nss, that's why it can be removed from thunderbird. I've added the ";required by nss.pc" inline comment locally next where it's propagated to mention why.
Hello, Maxim Cournoyer <maxim.cournoyer@gmail.com> writes: > nspr is now propagated by nss, that's why it can be removed from > thunderbird. I've added the ";required by nss.pc" inline comment > locally next where it's propagated to mention why. Ah perfect. My bad, I missed a nspr-next. In the current icedove there are there are icons at this path: "lib/icedove/chrome/icons/default". What's up with that? I only ask because you don't copy them to the wayland package and I don't know if that's an issue or not. Everything else LGTM, not that I'm actually a reviewer. Just an overly involved citizen. Morgan
Hi Morgan, Morgan Smith <Morgan.J.Smith@outlook.com> writes: > Hello, > > Maxim Cournoyer <maxim.cournoyer@gmail.com> writes: >> nspr is now propagated by nss, that's why it can be removed from >> thunderbird. I've added the ";required by nss.pc" inline comment >> locally next where it's propagated to mention why. > > Ah perfect. My bad, I missed a nspr-next. > > In the current icedove there are there are icons at this path: > "lib/icedove/chrome/icons/default". What's up with that? That's why it doesn't find its icon :-). Its icon per the icedove.desktop file should be named 'icedove', not default; the later seems to be a consequence of the re-branding. I basically copied the fix that is applied to IceCat. > I only ask because you don't copy them to the wayland package and I > don't know if that's an issue or not. About the icedove/wayland package, that appears to be a solely a wrapper, so I don't think the fix needs to be propagated there. > Everything else LGTM, not that I'm actually a reviewer. Just an overly > involved citizen. Your over-involvement is much welcome :-).
Hi Maxim, Maxim Cournoyer <maxim.cournoyer@gmail.com> writes: > About the icedove/wayland package, that appears to be a solely a > wrapper, so I don't think the fix needs to be propagated there. Since it's a wrapper the original files aren't installed into the profile, only the files in the wrapper. So if anyone wanted to look for icons at "lib/icedove/chrome/icons/default" they might be fine for the original package but not the wrapper. The wrapper copies "share" in though so the icons you copy there will be found just fine. I was simply questioning if someone else would try to find the icons at "lib/icedove/chrome/icons/default and if they would be out of luck since they don't exist in the wrapper. From what you're saying, it sounds like this isn't an issue at all because no-one cares about those icons. Also you might want to take a look at bug#61438 as someone is trying to update icedove. Also, the reason I discovered this patch series is because I expereinced bug#61438 and wanted to see if anyone had a fix ;). Morgan
Hi, Morgan Smith <Morgan.J.Smith@outlook.com> writes: > Hi Maxim, > > Maxim Cournoyer <maxim.cournoyer@gmail.com> writes: > >> About the icedove/wayland package, that appears to be a solely a >> wrapper, so I don't think the fix needs to be propagated there. > > Since it's a wrapper the original files aren't installed into the > profile, only the files in the wrapper. So if anyone wanted to look for > icons at "lib/icedove/chrome/icons/default" they might be fine for the > original package but not the wrapper. The wrapper copies "share" in > though so the icons you copy there will be found just fine. > > I was simply questioning if someone else would try to find the icons at > "lib/icedove/chrome/icons/default and if they would be out of luck since > they don't exist in the wrapper. > >>From what you're saying, it sounds like this isn't an issue at all > because no-one cares about those icons. Indeed, that's my understanding too. > Also you might want to take a look at bug#61438 as someone is trying to > update icedove. Also, the reason I discovered this patch series is > because I expereinced bug#61438 and wanted to see if anyone had a fix > ;). I see the above as been merged already, great! And I'll have more Icedove fixes coming that enables its language support.
diff --git a/gnu/packages/gnuzilla.scm b/gnu/packages/gnuzilla.scm index 15472ffed2..44e56a6573 100644 --- a/gnu/packages/gnuzilla.scm +++ b/gnu/packages/gnuzilla.scm @@ -1306,7 +1306,7 @@ (define-public icedove "ac_add_options --with-system-jpeg\n" "ac_add_options --with-system-libevent\n" "ac_add_options --with-system-nspr\n" - ;"ac_add_options --with-system-nss\n" + "ac_add_options --with-system-nss\n" "ac_add_options --with-system-zlib\n" "ac_add_options --without-wasm-sandboxed-libraries\n" "mk_add_options MOZ_MAKE_FLAGS=-j" @@ -1383,9 +1383,7 @@ (define-public icedove libxt mesa mit-krb5 - nspr-4.32 - ;; FIXME: create nss >= 3.68 after core-updates merge - ;;nss + nss-next pango pixman pulseaudio