2020-03-12T00:00:34 #kisslinux is there anybody here using a spotify client 2020-03-12T00:00:50 #kisslinux i can't find any that work with musl 2020-03-12T00:07:28 #kisslinux sirtomato: your best bet is librespot, but even then it's iffy 2020-03-12T00:07:38 #kisslinux otherwise, flatpak or web 2020-03-12T00:08:21 #kisslinux how does the web version work on FF cuz on chromium based you need widevine which only works on glibc cuz prop 2020-03-12T00:11:40 #kisslinux now that you mentioned it, the web version don't work in KISS, though I thought it was just because of KISS default configs, haven't tried it in Void though 2020-03-12T01:50:05 #kisslinux dylanaraps: The manpage's contents are https://manpage.me/?q=bash and the texinfo page's contents are https://tiswww.case.edu/php/chet/bash/bashref.html 2020-03-12T01:50:35 #kisslinux Some parts are identical, but the latter is way more comprehensive, with an introduction, example scripts, and such 2020-03-12T01:50:58 #kisslinux e.g., search for parallel 2020-03-12T01:54:21 #kisslinux I used a random webpage word counter and got 40314 words for the manpage and 71096 for the reference manual 2020-03-12T02:12:16 #kisslinux E5ten: printf %q "${var:=}a" gives me $'177a' which is delete. hm 2020-03-12T02:19:05 #kisslinux Also, how I interpreted illiliti's question was that they wanted to get the path of an external command. The solutions you posted only checks if the path returned is an external command 2020-03-12T02:19:32 #kisslinux You could use type -P for that in Bash, but I'm not sure what to do in POSIX 2020-03-12T02:20:50 #kisslinux https://pubs.opengroup.org/onlinepubs/9699919799/utilities/type.html 2020-03-12T02:20:52 #kisslinux OPTIONS - none 2020-03-12T02:21:02 #kisslinux Yes, that's why I said bash 2020-03-12T02:23:19 #kisslinux btw why do you need the external path? 2020-03-12T02:26:50 #kisslinux I think the most practical option would be which unless you're insistent on using builtins 2020-03-12T02:27:14 #kisslinux but then again, you're getting an external command's path, and I assume it's to execute it? if so, then you aren't using purely builtins anyway 2020-03-12T02:27:50 #kisslinux mksh has 'sleep' builtin. i need to copy external binaries and mksh breaks my script, that's why 2020-03-12T02:27:59 #kisslinux yeah, so just use which 2020-03-12T02:28:13 #kisslinux which is non posix 2020-03-12T02:28:26 #kisslinux ah you want pure posix hm 2020-03-12T02:28:39 #kisslinux yep 2020-03-12T02:35:15 #kisslinux well, manually searching the path might be the only way, then. 2020-03-12T02:47:40 #kisslinux although it seems that technically command -v should actually print the external path in posix 2020-03-12T02:48:41 #kisslinux and command might also have to be an external utility in posix so you could call `env command -v cmd` in that case to exclude builtins even if it didn't implement that 2020-03-12T02:49:08 #kisslinux but unfortunately most don't implement either. which is why pure posix can be ridiculous to follow sometimes 2020-03-12T03:31:26 #kisslinux dylanaraps: is there a way in POSIX sh to list all defined functions? 2020-03-12T08:33:33 #kisslinux E5ten: noop 2020-03-12T08:33:35 #kisslinux nope 2020-03-12T10:41:15 #kisslinux > configure: error: C++ compiler clang++ does not work or no compiler found 2020-03-12T10:41:20 #kisslinux ICU hard depends on clang now? 2020-03-12T10:53:01 #kisslinux compiler detects clang from your ccache I guess 2020-03-12T10:53:44 #kisslinux Ah 2020-03-12T10:53:45 #kisslinux Right 2020-03-12T10:55:02 #kisslinux This will be interesting to solve. 2020-03-12T10:55:36 #kisslinux > export CXX=${CXX:-cc} CC=${CC:-cc} 2020-03-12T10:55:39 #kisslinux That works 2020-03-12T10:56:12 #kisslinux Though this isn't an issue with the package 2020-03-12T10:56:17 #kisslinux It's a ccache issue 2020-03-12T10:56:43 #kisslinux Would you prefer I set CC/CXX or leave it as-is? 2020-03-12T10:57:05 #kisslinux I guess it doesn't matter for wyver* as it defaults to clang anyway. 2020-03-12T10:58:03 #kisslinux for your system, that's up to you, but for KISS, don't set CC/CXX, and for wyver* I maintain the build file myself so it would link to the default compiler only (clang) for now 2020-03-12T10:58:36 #kisslinux Alrighty 2020-03-12T10:59:00 #kisslinux > /usr/lib/gcc/x86_64-pc-linux-musl/10.0.1/../../../../x86_64-pc-linux-musl/bin/ld: makeconv.o:(.data.rel.local.DW.ref.__gxx_personality_v0[DW.ref.__gxx_personality_v0]+0x0): undefined reference to `__gxx_personality_v0' 2020-03-12T10:59:01 #kisslinux Fun 2020-03-12T10:59:17 #kisslinux > /usr/lib/gcc/x86_64-pc-linux-musl/10.0.1/../../../../x86_64-pc-linux-musl/bin/ld: ../../lib/libicui18n.so: undefined reference to `std::terminate()' 2020-03-12T10:59:22 #kisslinux A whole bunch of these 2020-03-12T10:59:37 #kisslinux > # The g++ compiler is less likely to support C++11. 2020-03-12T10:59:38 #kisslinux that's from gcc10? 2020-03-12T10:59:40 #kisslinux > # Make sure that we try clang++ first, which provides C++11 support. 2020-03-12T10:59:42 #kisslinux Yes 2020-03-12T11:01:34 #kisslinux I'm not sure which C++11 support are being talked about there but iirc gcc has support from it since gcc4.9 2020-03-12T11:01:39 #kisslinux s/from/for/ 2020-03-12T11:01:58 #kisslinux The older ICU version (the current one in the repos) works with GCC 10 2020-03-12T11:04:04 #kisslinux > /usr/lib/gcc/x86_64-pc-linux-musl/10.0.1/../../../../x86_64-pc-linux-musl/bin/ld: ../../lib/libicui18n.so: undefined reference to `std::terminate()' 2020-03-12T11:04:05 #kisslinux Actually 2020-03-12T11:04:09 #kisslinux It just fails later 2020-03-12T11:04:21 #kisslinux I'll make ICU depend on clang for the time being. 2020-03-12T11:57:10 #kisslinux dylanaraps: https://termbin.com/d0i7 2020-03-12T11:57:43 #kisslinux from your pure sh bible, only a bit modififed 2020-03-12T11:57:53 #kisslinux i call it `kat` lol 2020-03-12T11:58:37 #kisslinux things like EOF don't work though 2020-03-12T12:01:19 #kisslinux can it be possible? 2020-03-12T12:09:36 #kisslinux Anyone else having icu fail now? Tarball is 404? 2020-03-12T12:24:52 #kisslinux URL was wrong. 2020-03-12T12:59:42 #kisslinux My bad 2020-03-12T13:50:54 #kisslinux ?????? 2020-03-12T13:50:55 #kisslinux https://github.com/eqrion/cbindgen/releases/tag/'' 2020-03-12T13:51:04 #kisslinux Cbindgen version "''" released 2020-03-12T13:57:39 #kisslinux can i build firefox 2020-03-12T13:58:05 #kisslinux it takes 3 years but firefox-bin crashes all the time 2020-03-12T13:58:53 #kisslinux install firefox-privacy 2020-03-12T13:58:58 #kisslinux ok 2020-03-12T14:04:53 #kisslinux dylanaraps: https://termbin.com/buq9 2020-03-12T14:04:59 #kisslinux package list 2020-03-12T14:05:09 #kisslinux don't have a working browser atm 2020-03-12T14:05:15 #kisslinux (that supports js) 2020-03-12T14:06:52 #kisslinux i 2020-03-12T14:07:10 #kisslinux i'm rebuilding firefox 2020-03-12T14:07:20 #kisslinux root has a cbindgen build 2020-03-12T14:10:42 #kisslinux Okay Dylan I'll check the new sowm build in about 10 mins 2020-03-12T14:16:53 #kisslinux sirtomato: I'll be pushing a possible cbindgen fix in a few minutes. 2020-03-12T14:40:46 #kisslinux Hi dylanaraps. Still having the window movement lag with the new sowm master 2020-03-12T14:48:21 #kisslinux Damn 2020-03-12T14:48:25 #kisslinux I'll take a deeper look soon 2020-03-12T14:54:42 #kisslinux Okay, thanks though :) Silly question, but I haven't been able to find out much about this on the web. If I chroot into another distro from within KISS then start an X session, does it run from within that distro? And if so would it then be possible to symlink the config files from the actual KISS install? 2020-03-12T14:58:04 #kisslinux X can be configured to run GUI applications from a chroot, yeah. 2020-03-12T14:58:16 #kisslinux If you don't install the xauth package, it'll "just work". 2020-03-12T14:58:43 #kisslinux Ah okay. I don't know what the xauth package is. I'll read up on it now 2020-03-12T14:58:49 #kisslinux konimex: This was horrible to figure out. https://github.com/kisslinux/repo/commit/baec60ad1fde095f90251b9d08cde7fd09f51205 2020-03-12T15:00:47 #kisslinux Also. It turns out that our cbindgen package did need network... 2020-03-12T15:06:35 #kisslinux brb 2020-03-12T15:36:22 #kisslinux I hope those cargo crates are small enough 2020-03-12T15:38:16 #kisslinux It's no different to how it was 2020-03-12T15:38:36 #kisslinux Welcome to rust, go, npm, etc. 2020-03-12T15:38:38 #kisslinux Dependency hell 2020-03-12T15:41:51 #kisslinux I think you'd want to post the change and the rationale into the kiss weekly update, I kinda want to see the reaction from the fine people over at the linux subreddit (if they even care) 2020-03-12T15:43:33 #kisslinux Sure 2020-03-12T15:44:11 #kisslinux It shouldn't be this difficult to remove network 2020-03-12T15:44:34 #kisslinux 'cargo vendor' exists for the developer of the software to bundle everything into a tarball 2020-03-12T15:44:47 #kisslinux Nothing exists for the distributor of the software though 2020-03-12T15:44:53 #kisslinux "rationale": people have internet nowadays 2020-03-12T15:45:01 #kisslinux o/ 2020-03-12T15:45:22 #kisslinux The cargo registry is a git clone of 70MB~ to setup 2020-03-12T15:45:38 #kisslinux Were we to solely set 'CARGO_HOME=$PWD', there'd be a 70MB download each build 2020-03-12T15:45:44 #kisslinux to avoid touching $HOME 2020-03-12T15:46:07 #kisslinux It takes about 10 minutes on my net as a git clone is slower than a regular download 2020-03-12T15:46:54 #kisslinux I could add a special case to the package manager to automatically do this but then we fall down the path of special cases and I'd rather not go down this road 2020-03-12T15:47:45 #kisslinux yeah, afaic current approach works just fine, might want to add some guide to the style guide in case a developer thinks vendoring sucks though 2020-03-12T15:47:47 #kisslinux Hell, cbindgen has what 20~ dependencies? What about something like ripgrep which pulls down 100+ crates? 2020-03-12T15:48:59 #kisslinux konimex: The style guide for rust defaults to network as community is less strict about the no network requirement. 2020-03-12T15:49:35 #kisslinux alright 2020-03-12T15:49:38 #kisslinux Neovim is another example. It has a horrible build system and no ability to turn things off/on. It uses cmake to download during build 2020-03-12T15:50:23 #kisslinux Whereas regular vim has a modular build system and depends solely on ncurses at a minimum 2020-03-12T15:52:15 #kisslinux Ripgrep actually requires 45 crates 2020-03-12T15:52:42 #kisslinux It's still a lot though 2020-03-12T15:53:13 #kisslinux kiedtl: Have a look at this https://github.com/kisslinux/repo/commit/baec60ad1fde095f90251b9d08cde7fd09f51205 2020-03-12T15:54:25 #kisslinux > "rationale": people have internet nowadays 2020-03-12T15:54:50 #kisslinux only 45? 2020-03-12T15:54:56 #kisslinux The counter to this would be that the package manager can't then lock sources, do checksum verification and then sign this all with GPG. 2020-03-12T15:55:19 #kisslinux Cargo will sync with crates.io and change the required versions (sometimes(?)) 2020-03-12T15:55:31 #kisslinux """only""" 2020-03-12T15:55:32 #kisslinux ;) 2020-03-12T15:55:53 #kisslinux Hell, that's almost half of my installed packages 2020-03-12T15:55:59 #kisslinux for the entire system 2020-03-12T15:58:41 #kisslinux it's rare that I find a package that requires less than ~150 crates, I didn't know rg was so lightweight 2020-03-12T15:59:26 #kisslinux That's lightweight??? 2020-03-12T15:59:27 #kisslinux lol 2020-03-12T16:00:00 #kisslinux https://github.com/str4d/rage/blob/master/Cargo.lock#L1836 2020-03-12T16:00:08 #kisslinux rage requires 205 crates! 2020-03-12T16:00:23 #kisslinux That's insane 2020-03-12T16:01:34 #kisslinux I was working on a fetch program written in rust with a friend, it requires 210+ crates :( 2020-03-12T16:02:30 #kisslinux unfortunately the friend doesn't want to trim the dependencies, he/she says 200 crates is no big deal 2020-03-12T16:04:45 #kisslinux Your friend is wrong 2020-03-12T16:05:11 #kisslinux dylanaraps: so if I understand correctly cbindgen stores all crates locally? so no need to download them on build time? 2020-03-12T16:05:22 #kisslinux No 2020-03-12T16:05:27 #kisslinux I pre-download them 2020-03-12T16:05:33 #kisslinux See the sources file 2020-03-12T16:05:45 #kisslinux It connects to the net during build 2020-03-12T16:05:46 #kisslinux oh, nvm 2020-03-12T16:05:58 #kisslinux It just stores each crate as a source 2020-03-12T16:06:06 #kisslinux No 2020-03-12T16:06:11 #kisslinux I'm confused :( 2020-03-12T16:06:12 #kisslinux I do this all manually 2020-03-12T16:06:14 #kisslinux OK 2020-03-12T16:06:19 #kisslinux I'll explain 2020-03-12T16:08:34 #kisslinux Normal 'cargo build' will download all cbindgen dependencies (crates) from crates.io and store them into '~/.cargo'. They'll then be cached for rebuilds. 2020-03-12T16:09:09 #kisslinux This isn't a good thing as it then bypasses the locked dependencies (sources file), checksums (checksums file) and signature verification for the KISS repos and this information. 2020-03-12T16:09:30 #kisslinux Cargo can also change the dependencies of a package prior to the build 2020-03-12T16:09:44 #kisslinux And this all requires network during the build process 2020-03-12T16:10:06 #kisslinux My commit above changes cbindgen to download all of its dependency crates through the KISS package manager 2020-03-12T16:10:15 #kisslinux The sources file contains a generated list of urls 2020-03-12T16:10:30 #kisslinux I see 2020-03-12T16:10:31 #kisslinux The checksums of these are then a part of the KISS package 2020-03-12T16:10:49 #kisslinux I have to manually re-implement 'cargo vendor' to make cargo actually avoid network 2020-03-12T16:11:06 #kisslinux so if any one of those packages get's an update, those checksums have to be updated... 2020-03-12T16:11:08 #kisslinux I also have to set CARGO_HOME to prevent cargo from writing to ~/.cargo 2020-03-12T16:11:10 #kisslinux Yes 2020-03-12T16:11:31 #kisslinux darn, is that worth it? 2020-03-12T16:11:33 #kisslinux This can be fixed upstream if they run 'cargo vendor' before making their tarballs 2020-03-12T16:12:04 #kisslinux Well, if you want checksum verification, locked download sources, signature verification and no network during build, yes... 2020-03-12T16:12:28 #kisslinux These are a requirement for the official repositories (community excluded) 2020-03-12T16:12:37 #kisslinux It shouldn't be this difficult though 2020-03-12T16:13:00 #kisslinux I believe Gentoo and Debian do similar for their packages 2020-03-12T16:13:56 #kisslinux Ideally you'd just pop all of the .crate files into vendor/, run 'cargo build' and it'd all work. 2020-03-12T16:14:29 #kisslinux We have to extract each crate, generate checksums for all of them and create/populate a cargo config file on top of this 2020-03-12T16:16:13 #kisslinux This is why I don't like rust (and other "modern" languages with their own package managers). ;) 2020-03-12T16:17:28 #kisslinux When you have 200 additional moving parts on top of your own software, you're then trusting the code of 200+ people. 2020-03-12T16:18:13 #kisslinux rust is a very good language, it's just that cargo ruined it 2020-03-12T16:18:45 #kisslinux most rust programs are just short of the npm disease 2020-03-12T16:18:46 #kisslinux Everything is then expected to work... 2020-03-12T16:18:47 #kisslinux Dunno about you but I find this to be insane 2020-03-12T16:18:57 #kisslinux indeed 2020-03-12T16:19:08 #kisslinux anyway, rust is overkill for most things 2020-03-12T16:19:22 #kisslinux if robustness is key, then rust is the way to go 2020-03-12T16:19:32 #kisslinux otherwise, your better of sticking to raw C 2020-03-12T16:19:53 #kisslinux What I find odd is that rust (and cargo) also depend on crates 2020-03-12T16:19:58 #kisslinux A lot of them too 2020-03-12T16:21:01 #kisslinux idk why compilers tend to be written in their own programming language 2020-03-12T16:21:10 #kisslinux Hell, I have to do similar nonsense to prevent rust from downloading crap duing build 2020-03-12T16:21:15 #kisslinux during* 2020-03-12T16:21:16 #kisslinux it makes them A LOT harder to build 2020-03-12T16:21:24 #kisslinux Yup 2020-03-12T16:21:46 #kisslinux Rust takes forever to build too... 2020-03-12T16:22:05 #kisslinux > 181.2M total 2020-03-12T16:22:11 #kisslinux btw, what's the rust bootstrapping compiler written in? 2020-03-12T16:22:15 #kisslinux cpp or c? 2020-03-12T16:22:16 #kisslinux That's the size of the latest rust version on my system 2020-03-12T16:22:20 #kisslinux Rust 2020-03-12T16:22:25 #kisslinux It's a binary... 2020-03-12T16:22:32 #kisslinux wth 2020-03-12T16:22:35 #kisslinux Chicken and egg problem 2020-03-12T16:22:38 #kisslinux OK 2020-03-12T16:22:40 #kisslinux Listen to this 2020-03-12T16:22:57 #kisslinux To build rust without any binaries you have to go back years to the ocaml version. 2020-03-12T16:22:59 #kisslinux BUT 2020-03-12T16:23:06 #kisslinux Ocaml is also written in ocaml 2020-03-12T16:23:11 #kisslinux lmao 2020-03-12T16:23:28 #kisslinux So you need to go back to when ocaml wasn't written in ocaml 2020-03-12T16:23:48 #kisslinux iirc you can build ocaml using a C ocaml compiler 2020-03-12T16:23:53 #kisslinux I built ocaml once 2020-03-12T16:24:02 #kisslinux Once you get to ocaml built rust... You need to build each rust version ONE BY ONE from this point until the latest 2020-03-12T16:24:09 #kisslinux That's good to hear... 2020-03-12T16:24:31 #kisslinux We're talking 2015(?) rust till latest (5 or so years I believe) 2020-03-12T16:24:57 #kisslinux mrustc exists though 2020-03-12T16:25:00 #kisslinux Which is nice 2020-03-12T16:25:06 #kisslinux See: https://guix.gnu.org/blog/2018/bootstrapping-rust/ 2020-03-12T16:25:27 #kisslinux Still a fuck ton of rust builds till you get to latest though 2020-03-12T16:27:30 #kisslinux kiedtl: This is what led me to believe that ocaml is bootstrapped via binary: https://github.com/ocaml/ocaml/commit/84bbb2fd6f493112b43008a922b39e18e72dae54 2020-03-12T16:27:49 #kisslinux ie, there's a binary in the git repository for bootstrap 2020-03-12T16:28:06 #kisslinux oh, ok 2020-03-12T16:29:58 #kisslinux wath's this slack bot for? 2020-03-12T16:30:07 #kisslinux s/wath's/what's/g 2020-03-12T16:33:22 #kisslinux Because IRC is old I have to connect via Slack/Matrix/Discord/*? :^) 2020-03-12T16:35:38 #kisslinux SPEAKING OF RUST 2020-03-12T16:35:41 #kisslinux > Announcing Rust 1.42.0 2020-03-12T16:35:44 #kisslinux https://blog.rust-lang.org/2020/03/12/Rust-1.42.html 2020-03-12T16:57:28 #kisslinux :/quit 2020-03-12T16:57:37 #kisslinux lol, damn vim 2020-03-12T16:57:42 #kisslinux sorry (: 2020-03-12T16:58:48 #kisslinux lol 2020-03-12T16:58:57 #kisslinux This can be fixed upstream if they run 'cargo vendor' before making their tarballs << did you submit issue/bug to the upstream? 2020-03-12T16:58:59 #kisslinux Ctrl+C also works ;) 2020-03-12T16:59:13 #kisslinux illiliti: This may not be something they want to do. 2020-03-12T16:59:17 #kisslinux It's optional 2020-03-12T17:00:15 #kisslinux They don't actually release tarballs themselves either... 2020-03-12T17:00:30 #kisslinux They release a binary only 2020-03-12T17:00:34 #kisslinux lol 2020-03-12T17:00:36 #kisslinux So this is 100% something they won't do 2020-03-12T17:01:21 #kisslinux On the plus side... Our repositories are 100% network free (during build). For real this time! 2020-03-12T17:07:10 #kisslinux So this is 100% something they won't do << but why? i don't think that anyone like precompiled binaries 2020-03-12T17:11:02 #kisslinux They don't release a "dist" tarball. 2020-03-12T17:11:18 #kisslinux Only the GitHub pre-generated ones. 2020-03-12T17:12:07 #kisslinux The rust way (tm) is to do this through cargo 2020-03-12T17:12:20 #kisslinux ie, cbindgen is also on crates.io. 2020-03-12T17:12:31 #kisslinux It just so happens that GitHub also generate tarballs 2020-03-12T17:13:37 #kisslinux They could use CI to generate proper tarballs 2020-03-12T17:14:13 #kisslinux Sure 2020-03-12T17:14:39 #kisslinux We'd be getting them to do (arguably) needless work for no reason at all 2020-03-12T17:14:53 #kisslinux We're the exception and not the rule here ;) 2020-03-12T17:15:02 #kisslinux We're the weird ones who care about this 2020-03-12T17:36:14 #kisslinux > Building stage1 std artifacts (x86_64-unknown-linux-musl -> x86_64-unknown-linux-musl) 2020-03-12T17:36:18 #kisslinux Rust still building 2020-03-12T18:54:30 #kisslinux Rust still building! 2020-03-12T18:55:15 #kisslinux It's been three and a half hours 2020-03-12T18:56:57 #kisslinux which one? 2020-03-12T18:57:25 #kisslinux The latest release which came out 4~ hours ago 2020-03-12T18:57:37 #kisslinux 1.42.0 iirc 2020-03-12T18:58:08 #kisslinux for bootstrapping which version is needed? 2020-03-12T18:59:30 #kisslinux The rust bootstrap uses the previous release 2020-03-12T18:59:44 #kisslinux Though this is only for stage 0 which takes about 5 minutes to compile 2020-03-12T18:59:59 #kisslinux It's pointless using the system rust. 2020-03-12T19:00:58 #kisslinux i thought you use already installed rust version 2020-03-12T19:01:50 #kisslinux Nope 2020-03-12T19:02:05 #kisslinux Saves 5 minutes~ from the build process 2020-03-12T19:02:15 #kisslinux It's rather pointless 2020-03-12T19:02:34 #kisslinux The _one_ speedup we could gain is to skip building rust twice 2020-03-12T19:02:50 #kisslinux ie, we just use the first rustc, cargo, etc the bootstrap spits out 2020-03-12T19:03:00 #kisslinux Instead of verifying that the new rust can build rust 2020-03-12T19:03:26 #kisslinux just curious, when rust building will be like gcc 2020-03-12T19:04:02 #kisslinux The next rust version has a _lot_ of performance improvements on compile times 2020-03-12T19:04:07 #kisslinux their relase mostly use previous one 2020-03-12T19:04:11 #kisslinux We'll see how things progress 2020-03-12T19:04:43 #kisslinux ie, you can compile gcc 9.x with gcc 5.x isn't it 2020-03-12T19:04:53 #kisslinux but it is not valid in rust 2020-03-12T19:05:24 #kisslinux Nope 2020-03-12T19:05:36 #kisslinux See: https://guix.gnu.org/blog/2018/bootstrapping-rust/ 2020-03-12T19:05:56 #kisslinux i saw there 2020-03-12T19:06:01 #kisslinux It's a long process 2020-03-12T19:06:07 #kisslinux it does not make sense 2020-03-12T19:06:18 #kisslinux Rust has no stable ABI 2020-03-12T19:06:28 #kisslinux yeah, i wonder it 2020-03-12T19:06:43 #kisslinux when they plan a stable abi 2020-03-12T19:06:51 #kisslinux plan to release.. 2020-03-12T19:07:05 #kisslinux Never iirc 2020-03-12T19:07:45 #kisslinux https://github.com/rust-lang/rfcs/issues/600#issuecomment-526033825 2020-03-12T19:08:42 #kisslinux > It is my opinion (as a language team member but not speaking for the team as a whole) that Rust should never have a stable ABI for the default representation repr(Rust). 2020-03-12T19:08:50 #kisslinux https://github.com/rust-lang/rfcs/issues/600#issuecomment-526761006 2020-03-12T19:09:47 #kisslinux hmm 2020-03-12T19:09:53 #kisslinux thnks for links 2020-03-12T19:10:21 #kisslinux Also interesting (article and comments): https://old.reddit.com/r/rust/comments/aoebd5/swift_abi_stability_and_more/ 2020-03-12T19:13:01 #kisslinux lemme read 2020-03-12T19:14:20 #kisslinux This one too: https://drewdevault.com/2019/03/25/Rust-is-not-a-good-C-replacement.html 2020-03-12T19:18:32 #kisslinux yes, i read last one 2020-03-12T19:19:51 #kisslinux Rust is still building... 2020-03-12T19:19:55 #kisslinux ooo 2020-03-12T19:20:00 #kisslinux It's about to finish 2020-03-12T19:20:45 #kisslinux Huzzah 2020-03-12T21:21:13 #kisslinux question: when I submit/update a pkg in the community repo, I fork the repo. But once my PR is merged, the fork is out of date. However, updating the fork means adding an extra merge commit, so future PR's won't work. 2020-03-12T21:21:19 #kisslinux any way around this? 2020-03-12T21:21:29 #kisslinux pretty sure I'm doing something exceptionally dumb. 2020-03-12T21:36:46 #kisslinux dylanaraps: would it be reasonable to remove the x86-64-specific options from kiss-chroot? If not, no probs I'll just fork. 2020-03-12T21:59:05 #kisslinux jedavies: See latest commit ($2 sets arch) 2020-03-12T21:59:14 #kisslinux kiedtl: You can use branches 2020-03-12T22:06:59 #kisslinux Nice... can you also include the "-mtune=generic" option in the default for $2? -mtune=generic works on aarch64 but is not valid on powerpc64le. 2020-03-12T22:08:33 #kisslinux dylanaraps: so, once the branch with my changes is merged into kisslinux/community, my fork will still be out of date. 2020-03-12T22:08:47 #kisslinux which means that I'll have to pull from upstream into my fork, adding a merge commit. 2020-03-12T22:10:10 #kisslinux jedavies: Sure 2020-03-12T22:10:25 #kisslinux Did I break the resolve.conf or did it get set automatically when I installed? 2020-03-12T22:10:45 #kisslinux Shyiskhar: It's copied from host (if it doesn't exist) when you use kiss-chroot 2020-03-12T22:12:23 #kisslinux kiedtl: You could rebase and force push to your PR. 2020-03-12T22:12:42 #kisslinux kiedtl: Or you just 'git rebase' on community. 2020-03-12T22:12:45 #kisslinux Lots of options. 2020-03-12T22:13:06 #kisslinux jedavies: https://github.com/kisslinux/kiss/commit/4cbe2cb42e76f2cd3ea29fe4ff0de0090df7d8ac 2020-03-12T22:15:16 #kisslinux Thanks, that's great! 2020-03-12T22:22:57 #kisslinux dylanaraps: ok, thanks! 2020-03-12T22:25:08 #kisslinux Just noticed in CXXFLAGS it has ---march=x86-64 instead of --march=x86-64 2020-03-12T23:28:39 #kisslinux im trying to download the kiss-chroot rn, and current speeds are ~20KB/s 2020-03-12T23:28:46 #kisslinux damn, this is going to take a while 2020-03-12T23:29:26 #kisslinux oh, nevermind? it just finished 2020-03-12T23:47:10 #kisslinux ok cool, im working on installing KISS now