💾 Archived View for gemini.ctrl-c.club › ~phoebos › logs › freenode-kisslinux-2020-10-04.txt captured on 2021-12-17 at 13:26:06.
-=-=-=-=-=-=-
2020-10-04T04:58:00 #kisslinux <dylanaraps> kciN: If the keyserver in the documentation fails to work, try another one
2020-10-04T05:05:50 #kisslinux <dylan02> I'm trying out kirc :)
2020-10-04T06:59:13 #kisslinux <dylanaraps> I've released 6.0.0 as a pre-release so that users can test it prior to release. https://github.com/kisslinux/kiss/releases/tag/6.0.0 I have also pushed 6.0.0 to the testing repository.
2020-10-04T06:59:39 #kisslinux <dylanaraps> For those willing to test, please let me know of any bugs, regressions or issues. :)
2020-10-04T07:05:19 #kisslinux <konimex> > Packages linking to these libraries should either have the dependency removed (if it makes sense)
2020-10-04T07:05:34 #kisslinux <konimex> not sure what this means
2020-10-04T07:07:02 #kisslinux <dylanaraps> konimex: libgcc dependency may be optional in some cases.
2020-10-04T07:07:26 #kisslinux <dylanaraps> Depends on what it is being used for.
2020-10-04T07:08:44 #kisslinux <dylanaraps> Though in most cases, nothing will change (except for gcc now being present in depends files)
2020-10-04T07:09:39 #kisslinux <dylanaraps> Same goes for llvm of course
2020-10-04T07:09:48 #kisslinux <konimex> so every single C++ package will have gcc/llvm depends? (except statically linked pkgs, but personally not a fan of it)
2020-10-04T07:11:08 #kisslinux <dylanaraps> No
2020-10-04T07:11:23 #kisslinux <dylanaraps> Only those that link to gcc/llvm libraries.
2020-10-04T07:12:37 #kisslinux <dylanaraps> I'll go through and build the entire repositories later today to see the extent of the change.
2020-10-04T07:12:49 #kisslinux <konimex> all C++ packages link to gcc (libstdc++.so) or llvm (libc++.so) though
2020-10-04T07:13:09 #kisslinux <konimex> but yeah, it'll make rebuilds easier in case one wants to migrate to either
2020-10-04T07:13:48 #kisslinux <konimex> though I don't think building gcc from clang is possible as of now
2020-10-04T07:14:03 #kisslinux <dylanaraps> The question is whether they /should/ remain "hidden" or not.
2020-10-04T07:15:09 #kisslinux <dylanaraps> I can suppress libstdc++/libc++ and only show dependencies from libgcc_s and whatever the compiler-rt library is called.
2020-10-04T07:15:31 #kisslinux <dylanaraps> How does that sound as some sort of middle ground?
2020-10-04T07:15:48 #kisslinux <dylanaraps> Or we can revert back to hiding all of it.
2020-10-04T07:16:22 #kisslinux <dylanaraps> If we decided to revert, implementation will swap to being file based rather than package based. We were hardcoding 'gcc' and 'llvm' when I think it's better we hardcode the names of the libraries themselves.
2020-10-04T07:16:53 #kisslinux <dylanaraps> Example: A 'gcc-git' package will not be correctly handled in the dependency fixer in the current release.
2020-10-04T07:17:05 #kisslinux <dylanaraps> (As we only look at 'gcc')
2020-10-04T07:18:17 #kisslinux <dylanaraps> 6.0.0 is still a pre-release and I'm open to making any necessary changes prior to final. Nothing is set in stone.
2020-10-04T07:18:26 #kisslinux <konimex> I think now's fine
2020-10-04T07:18:48 #kisslinux <dylanaraps> Behavior in master is fine you mean?
2020-10-04T07:18:58 #kisslinux <dylanaraps> Or behavior in 5.X.X?
2020-10-04T07:19:09 #kisslinux <konimex> if they switch implementations they'll likely need to rebuild everything anyway, so be as explicit as possible
2020-10-04T07:19:13 #kisslinux <konimex> the master behavior
2020-10-04T07:20:31 #kisslinux <dylanaraps> Also, I've not noticed any issues with globally setting '-static-libgcc -static-libstdc++' for reference. This might be something users will be interested in.
2020-10-04T07:22:11 #kisslinux <dylanaraps> konimex: Users shouldn't go around adding gcc to every depends file though. This should be reserved solely for the depends fixer... otherwise there will be issues with packages demanding gcc when llvm/clang can also be used.
2020-10-04T07:22:13 #kisslinux <dylanaraps> Make sense?
2020-10-04T07:23:26 #kisslinux <konimex> sure
2020-10-04T07:33:19 #kisslinux <dylanaraps> konimex: What are the equivalent .so files from llvm/clang called?
2020-10-04T07:33:39 #kisslinux <dylanaraps> libc++.so covers libstdc++.so
2020-10-04T07:33:46 #kisslinux <dylanaraps> What about libgcc_s?
2020-10-04T07:34:49 #kisslinux <dylanaraps> libclang_rt.*.so ?
2020-10-04T07:35:23 #kisslinux <dylanaraps> libclang.so / libclang-cpp.so ?
2020-10-04T07:35:41 #kisslinux <konimex> for compiler-rt it should be libclang_rt.*.so
2020-10-04T07:35:56 #kisslinux <dylanaraps> Thanks
2020-10-04T07:35:57 #kisslinux <konimex> for C++ lib there's also libc++abi
2020-10-04T07:36:06 #kisslinux <dylanaraps> Anything else?
2020-10-04T07:36:22 #kisslinux <konimex> two secs
2020-10-04T07:37:49 #kisslinux <konimex> there's libLLVM-.so and libclang-.so but I think they should be explicitly added
2020-10-04T07:38:22 #kisslinux <dylanaraps> Yeah. I'm wanting just the compiler runtimes
2020-10-04T07:39:42 #kisslinux <konimex> there's also libunwind.so
2020-10-04T07:40:26 #kisslinux <konimex> and that's about it for now
2020-10-04T07:42:06 #kisslinux <dylanaraps> I think it's best we keep them explicit but maintain that gcc/llvm not be added to depends files if only the runtime libraries are needed.
2020-10-04T07:42:35 #kisslinux <dylanaraps> ie libgcc_s / libstdc++ / etc
2020-10-04T07:42:44 #kisslinux <konimex> sure
2020-10-04T07:44:11 #kisslinux <dylanaraps> Problem with the current method is that 'kiss r gcc' may be unguarded due to the fixer not doing its thing. Removal of gcc will then break anything linking to libgcc_s or libstdc++.
2020-10-04T07:44:42 #kisslinux <dylanaraps> Making it explicit solves this by properly correcting depends files (at the expense of some noise)
2020-10-04T07:46:10 #kisslinux <dylanaraps> We /could/ guard against gcc/llvm removal in all cases, show a warning message about runtime libraries and state that KISS_FORCE must be used. We could then keep them hidden without issue.
2020-10-04T07:46:21 #kisslinux <dylanaraps> I'll spend some time thinking about how we want to move forward.
2020-10-04T07:47:06 #kisslinux <dylanaraps> I'll be on a little later. Going for a walk. o/
2020-10-04T08:56:19 #kisslinux <muevoid> Does bc have a tangent function?
2020-10-04T09:10:54 #kisslinux <lpy> hmm, the man-page mentions the sin, cos and tan¯¹ functions
2020-10-04T09:12:02 #kisslinux <muevoid> Thanks
2020-10-04T09:12:11 #kisslinux <muevoid> I just found a different one on github :P
2020-10-04T09:12:25 #kisslinux <muevoid> It seems to work better for me atm
2020-10-04T09:12:28 #kisslinux <muevoid> But thank you
2020-10-04T09:12:43 #kisslinux <lpy> ah, which one is it
2020-10-04T09:13:29 #kisslinux <muevoid> Just searched calculator on github sorted by c and chose the first one lol
2020-10-04T09:13:46 #kisslinux <lpy> https://github.com/sharkdp/insect
2020-10-04T09:14:00 #kisslinux <muevoid> Has tangent and stuff like setting degrees or radians
2020-10-04T09:14:39 #kisslinux <muevoid> Yeah I saw that but not a huge fan of thinks in js
2020-10-04T09:15:10 #kisslinux <lpy> yeah me neither, and this one is a bit over-the-top
2020-10-04T09:17:32 #kisslinux <muevoid> things*
2020-10-04T09:17:39 #kisslinux <muevoid> Yeah
2020-10-04T09:17:54 #kisslinux <muevoid> I am probably going to try and figure out bc at some point but just needed something for now
2020-10-04T09:56:45 #kisslinux <lpy> the syntax sucks lol, eg; the tangent of 30° looks something like
2020-10-04T09:56:46 #kisslinux <lpy> bc -l <<< "s((4*a(1))/6)/c((4*a(1))/6)"
2020-10-04T10:06:47 #kisslinux <muevoid> Holy
2020-10-04T10:06:50 #kisslinux <muevoid> Lol
2020-10-04T11:23:03 #kisslinux <muevoid> o/
2020-10-04T11:29:48 #kisslinux <dylanaraps> o/
2020-10-04T14:27:59 #kisslinux <claudia02> dylanaraps: what do you think about giving 'kiss-outdated' some color?
2020-10-04T14:30:20 #kisslinux <claudia02> for better overview. Otherwise I like it very much.
2020-10-04T14:38:25 #kisslinux <jedavies> konimex: do you know a way of preventing clang/llvm from linking to libexecinfo if it's present?
2020-10-04T14:46:54 #kisslinux <konimex> jedavies: from a quick glance to both of their CMakeLists, I don't think they ever link to libexecinfo
2020-10-04T15:19:09 #kisslinux <jedavies> konimex: if libexecinfo is present when building llvm/clang then clang and libLLVM-11.0.0.so link to libexecinfo.so.1
2020-10-04T15:19:45 #kisslinux <jedavies> If I then do kiss-reset I don't have a working compiler! So I'd like to explicitly stop this from linking.
2020-10-04T15:20:20 #kisslinux <jedavies> Will have a look through the source later
2020-10-04T15:23:36 #kisslinux <E5ten> dylanaraps konimex: for compiler-rt, it's only a static lib anyway isn't it? So it wouldn't be a dep I think?
2020-10-04T15:25:32 #kisslinux <konimex> E5ten: from my experience I never encountered a dynamic library from compiler-rt, but looking from Arch's compiler-rt, there are libclang-*.so, don't know what black magic they do, but I think it's make a safe precaution in case someone's managed to do it
2020-10-04T15:25:54 #kisslinux <konimex> s/it's make/it's more of/
2020-10-04T15:27:37 #kisslinux <E5ten> I think those are probably the sanitizers and stuff
2020-10-04T15:28:11 #kisslinux <E5ten> The part that's a parallel for libgcc_s is only static afaik
2020-10-04T18:03:11 #kisslinux <jedavies> Added this in the build to prevent llvm linking to libexecinfo: sed -i 's/set(HAVE_BACKTRACE ${Backtrace_FOUND})/set(HAVE_BACKTRACE 0)/g' llvm/cmake/config-ix.cmake
2020-10-04T18:03:41 #kisslinux <jedavies> Seems Backtrace_FOUND is true if execinfo.h is present.
2020-10-04T19:44:01 #kisslinux <dilynm> dylanaraps: testing out kiss. I love the looks of kiss-outdated now!
2020-10-04T19:44:22 #kisslinux <dilynm> Can we get it to exclude git packages
2020-10-04T20:28:18 #kisslinux <dilynm> For packages like the kernel, system time on install is halved but wall time only drops by 5 seconds. But it's under a minute, which seems reaaaallll gucci
2020-10-04T20:28:35 #kisslinux <onodera> there is a kernel package?
2020-10-04T20:32:02 #kisslinux <soliwilos> onodera: If you either make one or copy one from someone's git, then yes. :-p
2020-10-04T21:28:15 #kisslinux <Rio6> startx segfaults after kiss u, not sure if it's me messing up :P
2020-10-04T21:28:27 #kisslinux <Rio6> also what's the easiest way to get manpages working
2020-10-04T21:58:38 #kisslinux <mcpcpc[m]> https://k1ss.org/wiki/software/man-pages
2020-10-04T22:00:14 #kisslinux <Rio6> ah thanks, I was missing mandoc
2020-10-04T22:00:30 #kisslinux <Rio6> I still need to rebuild packages myself tho if I want their man page
2020-10-04T22:00:31 #kisslinux <Rio6> right?
2020-10-04T22:01:32 #kisslinux <mcpcpc[m]> you should check and see what is in the manifest
2020-10-04T22:02:13 #kisslinux <mcpcpc[m]> if not, then you can request the package owner to add it or rebuild yout own
2020-10-04T22:02:27 #kisslinux <Rio6> for those that don't come with man pages I mean
2020-10-04T22:02:27 #kisslinux <Rio6> yeah