03:01 <sad_plan> what would be a effecient way of using an alternative util? instead of the alternative system.

03:01 <sad_plan> i.e., if your tar implentation is broken for 1 package, and youd rather use busybox's. as an example

03:02 <sad_plan> an alias?

03:02 <sad_plan> Im thinkin in the line of in a buildscript

03:03 <sad_plan> in this case, alias tar=busybox tar inside the buildscript

04:42 <testuser[m]> sad_plan: just don't use broken utils

04:42 <testuser[m]> Hi

04:43 <sad_plan> now thats not very helpfull is it

04:45 <sad_plan> in any case, would an alias work sufficently? or is there a better solution?

05:24 <sewn> testuser: I forgor

05:24 <sewn> Hi

05:56 <Ellowee[m]> <sad_plan> "in any case, would an alias work..." <- Having a spare around

15:28 <sad_plan> Ellowee[m]: wdym?

19:56 <midfavila> an alias would wor

19:56 <midfavila> work*

20:40 <Ellowee[m]> <sad_plan> "Ellowee: wdym?" <- A backup binary

21:27 <sad_plan> thanks midfavila. I thought as such, but I was unsure if it would work as one would expect

21:28 <sad_plan> Ellowee[m]: I dont see how that would work. wouldnt I either have to ship the binary on those packages, or build them, just not install them, or whats your idea here? :p

21:28 <midfavila> yw bby

21:28 <sad_plan> <3

21:28 <midfavila> <3~

23:46 <noocsharp> anyone with gnu coreutils installed: what's the output of `printf "aa" | basenc -d --base64`?

23:48 <sad_plan> hm, im not sure im doing this right. so, after some digging, I found out aliases isnt expanded in non-interactive shells. which is fine. I thought I could just put it into the buildscript, but no.

23:49 <sad_plan> I thought I could just make a file with the aliases present, and source it, but that didnt seem to work either

23:51 <midfavila> i suppose i was wrong

23:51 <midfavila> who could have seen that coming

23:51 <midfavila> coulda sworn it would've worked, sorry for the false lead

23:51 <sad_plan> seems something else is wrong. im going to check some other package

23:52 <sad_plan> nss was the package I tried, but it seems theres an issue with the sed. built last week though when I just added a switch for sed and tr. strange

23:52 <sad_plan> no biggie at all mid. doing research on this is good for me anyway

23:55 <sad_plan> http://0x0.st/oFEm.sh the sed on beginning at line 39 seems to break for some reason. im I missing something? I didnt really change anything when I forked the package