groovy2shoes has quit [Remote host closed the connection]
groovy2shoes has joined #crux-devel
darfo has quit [Ping timeout: 268 seconds]
darfo has joined #crux-devel
crash_ has quit [Remote host closed the connection]
crash_ has joined #crux-devel
SiFuh_ has quit [Ping timeout: 260 seconds]
SiFuh has joined #crux-devel
groovy2shoes has quit [Ping timeout: 240 seconds]
<jaeger>
I think we've talked about it in the past but I'm running into another port where it would be handy to exclude a specific archive in the source=() array from being extracted
<jaeger>
In this case it's osinfo-db - installation of it is done with a tool called directly on the archive, not with extracted files
<jaeger>
http://ix.io/45R9 <-- so instead of doing this (overriding the unpack_source function) it might be useful to have a way to flag a source file to be left alone instead of unpacked automagically
groovy2shoes has joined #crux-devel
<farkuhar>
jaeger: my preferred method is to use the renames=() array so that the pattern matching performed by unpack_source will copy the file intact. Then do whatever you want with the renamed file inside build(). Here's python3-babel, for example: http://ix.io/45Ru
<farkuhar>
python3-wheel is another interesting case where unpack_source is overridden by the Pkgfile, but there it was not the intention to leave the archive intact. Overriding unpack_source in that case might have been motivated by bsdtar behaving weirdly on that particular archive, while gnu tar has no such problems.
<farkuhar>
I can't remember whether the weird behaviour of bsdtar on the python3-wheel source had anything to do with LC_ALL or C.UTF-8, but maybe that port can be revisited now that 3.7 is undergoing wider testing.