-
Notifications
You must be signed in to change notification settings - Fork 17
Conversation
Bai, try to run a basic self-build check.. |
build/20-ruby.sh
Outdated
rm "$PKGDIR/$GEMDIR/cache/$PKGNAME-$PKGVER.gem" | ||
GEMDIR="$(ruby -e'puts Gem.default_dir')" | ||
gem install --ignore-dependencies --no-user-install -i "$PKGDIR/$GEMDIR" -n "$PKGDIR/usr/bin" "$PKGNAME-$PKGVER.gem" | ||
rm -f -- "$PKGDIR/$GEMDIR/cache/$PKGNAME-$PKGVER.gem" |
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.
Should I simply nuke all the cache?
pm/dpkg/pack
Outdated
DPKGDEBCOMP+="-z6" | ||
fi | ||
} | ||
if [[ " ${DPKGDEBCOMP[*]" == *' '-z* ]]; then |
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.
wtf
rebased. still recommending |
Well, OK, f that, I forgot to check the args in arch/_common. |
Since the flags are exported into ENV in the traditional sloppy way anyway, there is no point in array-izing it for now. |
How is this PR now? |
Changes required for merging should be still obvious. |
Oh. The flags internal part (nolto, usexxx etc) needs some data sanitization too. |
9f69b9d
to
f31dcd8
Compare
lmao this isn't going anywhere. Anyways, just came up with these snippets:
|
This has stalled for way too long and requires quite a bit of work still. Let's resurrect this when we feel up for it. |
#62