New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
libreoffice-fresh: 6.4.3.2 -> 7.0.0.3 #96474
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Code looks fine to me
Currently building. I've seen some warnings pass by like these:
Doesn't really matter because it's just a warning, but I was wondering if there's an override in nixpkgs for CXXFLAGS instead of all CFLAGS? I'll go to sleep now and give an update on how it works when I wake up :) (and have some time). |
url = "http://dev-www.libreoffice.org/src/../extern/odfvalidator-1.2.0-incubating-SNAPSHOT-jar-with-dependencies-971c54fd38a968f5860014b44301872706f9e540.jar"; | ||
sha256 = "984f2a479df79e27e7b01a5815ac53ae64e07746b882262d8a64566494515504"; | ||
name = "odfvalidator-0.9.0-RC2-SNAPSHOT-jar-with-dependencies-2726ab578664434a545f8379a01a9faffac0ae73.jar"; | ||
url = "http://dev-www.libreoffice.org/src/../extern/odfvalidator-0.9.0-RC2-SNAPSHOT-jar-with-dependencies-2726ab578664434a545f8379a01a9faffac0ae73.jar"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a reason for keeping the /src/../extern/
like that? It can be replaced with just /extern/
, no?
Is there a reason for keeping the `/src/../extern/` like that? It can be replaced with just `/extern/`, no?
I am not sure it is guaranteed for HTTP paths, but probably it is true in every reasonable case.
But as these files are generated, it makes sense to keep the simplest generator that works as long as it keeps working…
|
Oh, I didn't know it was generated. Then of course it doesn't really matter. Just keep it as-is. Everything built and seems to work fine. I see some warnings (during saving in writer) but they're probably not nix-specific, so I think it's all good. I've tried to run all binaries and they all seem to work as expected.
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Builds and works for me.
Motivation for this change
Better MS support.
https://wiki.documentfoundation.org/ReleaseNotes/7.0
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)