Could you at the very least test it yourself unstead of just assuming it will "likely" not work? I wouldn't be doing it myself this way if it wouldn't work. The only time it won't find libraries is if you don't set your LD_LIBRARY_PATH approprietely: export LD_LIBRARY_PATH=~/.local/lib:$LD_LIBRARY_PATH Again, we have .bashrc or .zshrc for that. The other possibility is that header files are hardcoded to something like "#include " rather than "#include ", but you really have to be the dumbest developer on the face of the Earth to even do that. On 2023年08月17日 21:30, Doug Newgard wrote:

On Fri, 18 Aug 2023 11:00:37 +0900 "lain." wrote:

...

This is how I have set it up: /usr/bin = systemwide binaries /usr/lib = systemwide libraries ~/.local/bin = user binaries ~/.local/lib = user libraries

I don't really like to use /usr/local/* on Linux, because it's not as portable as just /usr. I use it only in FreeBSD and OpenBSD, simply because it's the default behavior there.

If you compile from source (includes AUR): ./configure --prefix="~/.local" make DESTDIR="~/.local" install

If directly from the pacman repo's: pacman -S android-ndk -r ~/.local -b /var/lib/pacman The one downside of that is that it'll install for example "android-tools" under ~/.local/usr/bin rather than ~/.local/bin though, but with a bit of manual labor, you can correct that.

Then in your .bashrc or .zshrc: export PATH=~/.local/bin:$PATH

This way you can install multiple versions of software, and binaries in ~/.local will take preference over those in /usr, and you can always just run /usr/bin/whatever if you want to run the systemwide version instead.

And none of them are likely to work. It'll have no way to find it's libraries or other resources. You CANNOT use pacman for something like this.

-- lain.

Not sure what you mean by "top posting", but JAWOHL MEIN FUHRER!! On 2023年08月18日 07:20, Doug Newgard wrote:

On Fri, 18 Aug 2023 15:31:21 +0900 "lain." wrote:

...

Could you at the very least test it yourself unstead of just assuming it will "likely" not work? I wouldn't be doing it myself this way if it wouldn't work. The only time it won't find libraries is if you don't set your LD_LIBRARY_PATH approprietely: export LD_LIBRARY_PATH=~/.local/lib:$LD_LIBRARY_PATH Again, we have .bashrc or .zshrc for that.

The other possibility is that header files are hardcoded to something like "#include " rather than "#include ", but you really have to be the dumbest developer on the face of the Earth to even do that.

And when it has to load images, icons, config files, etc? No, it's extremely unlikely to work. Do not do this.

And stop top posting.

-- lain.

I see lots of weird newspeak here, but just outright dictating me how to write emails even though there's no law criminalizing the act of replying to emails as 100% of all email clients do by default is not really what I consider to be respective or inclusive either. And yes, I had to look up what "top posting" means. On 2023年08月19日 10:14, Robin Candau wrote:

Le 19/08/2023 à 09:14, lain. a écrit :

...

Not sure what you mean by "top posting", but JAWOHL MEIN FUHRER!!

Please, do not make use of those kind of poor and controversial jokes/references within the Arch community:

- https://terms.archlinux.org/docs/code-of-conduct/#respect-other-users - https://terms.archlinux.org/docs/code-of-conduct/#no-trolling - https://terms.archlinux.org/docs/code-of-conduct/#controversycontroversial-t...

-- Regards, Robin Candau / Antiz

-- lain.

I see lots of weird newspeak here, but just outright dictating me how to write emails even though there's no law criminalizing the act of replying to emails as 100% of all email clients do by default is not really what I consider to be respective or inclusive either. While there's no "law criminalizing top posting", there are general guidelines for Arch mailing list posting style [1] that you should adopt and follow as a member of this community which imply **not** to top

Le 19/08/2023 à 10:57, lain. a écrit : posting [2]. And yes, I

had to look up what "top posting" means. And yet you're still doing it :)

[1] https://wiki.archlinux.org/title/General_guidelines#Mailing_lists [2] https://wiki.archlinux.org/title/General_guidelines#Top_posting -- Regards, Robin Candau / Antiz

On 2023年08月19日 14:47, Polarian wrote:

Hello,

I would like to point out the fact top posting (or bottom posting) both cause major issues in most mailing lists.

A lot of email clients sort emails into "threads", in which you can see all previous emails (provided you were subscribed to the mailing list since the beginning of said thread), otherwise you can always check the archives to see what you have missed.

Keeping a "transcript" of sorts of all the emails sent in the thread produces huge emails, some mailing list threads span 30-50 emails, with varying lengths. If you top post (or bottom post) that entire chain is appended to the top or bottom respectively.

I have seen a few arguments on previous threads where people "delete the thread history therefore want to be able to see all previous emails", however the solution to this is simple, just don't delete mailing list emails, they take up what? 10-20KB if they are small (or if they are sent by me, probably a good few hundred KB's :P).

And for future reference, always check the mailing list rules, for example I got crucified on the OpenBSD mailing list because I sign my emails by default with my GPG key, OpenBSD want unsigned plain text emails, meanwhile the Arch Mailing Lists are open to signing, and in fact required by arch staff (I do not know if general responses need to be signed, or just applications/formal emails, maybe a TU could clarify?).

TL;DR keep your emails as small and concise as possible, while also not being too vague that nobody is able to help you (for example reporting an issue and then not providing any logs or steps to reproduce said problem). And yes for those laughing at the fact I am the one saying this, I am aware I am extremely verbose, never said I was any good at this :P

Hope this helps!

Take care, -- Polarian GPG signature: 0770E5312238C760 Website: https://polarian.dev JID/XMPP: polarian@icebound.dev

I can try to bottom post, it's going to take a while to adjust to it. Even to this day I mistakenly reply to single people instead of the mailing list, just because the key binding to reply to an email is "r", whereas the key binding to reply to a mailing list is "L" on neomutt. As for OpenBSD, I post there pretty often, and I got crucified for all sorts of things, but signing with PGP is not one of them. More for things like not using the default tools, having a text signature (the one you'll see after "lain."), using GnuPG for PGP (or any GNU tool for that matter), and other non-issues. In fact, I always sign with PGP, no exceptions. But overall, I really enjoy mailing lists a lot, it's like a web-based forum, but without all the bloat, and all from an email client. No wonder Linus Torvalds has been using this from day 1, and still does to this day! :) -- lain. Did you know that? 90% of all emails sent on a daily basis are being sent in plain text, and it's super easy to intercept emails as they flow over the internet? Never send passwords, tokens, personal information, or other volunerable information without proper PGP encryption! If you're writing your emails unencrypted, please consider sending PGP encrypted emails for security reasons. You can find my PGP public key at: https://fair.moe/lain.asc Every good email client is able to send encrypted emails. If yours can't, then you should consider switching to a secure email client, because yours just sucks. My recommendations are Claws Mail or NeoMutt. For instructions on how to encrypt your emails: https://unixsheikh.com/tutorials/gnupg-tutorial.html

On 2023年08月19日 16:06, Polarian wrote:

Why are you set out to try to be controversial.

I'm not trying to be controversial at all, I'm just using email like how email is intended to be used, that's all. You're the one who accuses me of "being controversial". On 2023年08月19日 16:06, Polarian wrote:

How hard is it to just quote what is needed? (Like I have just done here)

How hard is it to not be so damn bossy, I'm not your servant! Yes, there are rules, and I do my best to follow them, but there's a line to be drawn between pointing out there are certain rules, and being absolutely anal about the smallest detail possible. -- lain. Did you know that? 90% of all emails sent on a daily basis are being sent in plain text, and it's super easy to intercept emails as they flow over the internet? Never send passwords, tokens, personal information, or other volunerable information without proper PGP encryption! If you're writing your emails unencrypted, please consider sending PGP encrypted emails for security reasons. You can find my PGP public key at: https://fair.moe/lain.asc Every good email client is able to send encrypted emails. If yours can't, then you should consider switching to a secure email client, because yours just sucks. My recommendations are Claws Mail or NeoMutt. For instructions on how to encrypt your emails: https://unixsheikh.com/tutorials/gnupg-tutorial.html

On Sat, 19 Aug 2023 17:57:51 +0900 "lain." wrote:

I see lots of weird newspeak here, but just outright dictating me how to write emails even though there's no law criminalizing the act of replying to emails as 100% of all email clients do by default is not really what I consider to be respective or inclusive either. And yes, I had to look up what "top posting" means.

On 2023年08月19日 10:14, Robin Candau wrote:

...

Le 19/08/2023 à 09:14, lain. a écrit :

...

Not sure what you mean by "top posting", but JAWOHL MEIN FUHRER!!

Please, do not make use of those kind of poor and controversial jokes/references within the Arch community:

- https://terms.archlinux.org/docs/code-of-conduct/#respect-other-users - https://terms.archlinux.org/docs/code-of-conduct/#no-trolling - https://terms.archlinux.org/docs/code-of-conduct/#controversycontroversial-t...

-- Regards, Robin Candau / Antiz

Top posting running windows or macentoy This is the correct place to reply not above . Pete

On Fri, 18 Aug 2023 11:00:37 +0900 "lain." wrote:

If directly from the pacman repo's: pacman -S android-ndk -r ~/.local -b /var/lib/pacman

Hi, this complains I am not root. I don't really want to have root-owned files in my home dir; also I'm curious, does pacman remember to write android-ndk to this location when upgrading?

On Fri, 18 Aug 2023 16:38:28 +0900 "lain." wrote:

Though it is possible to make it do so, but requires quite a bit of workarounds, like copying over all the files and directories pacman uses (/var/lib/pacman, /usr/share/pacman, /etc/pacman*, and so on) to your home directory (or separate partition), and you'll need to pass the "--sysroot" flag every time you want to update, so it's a bit anal.

Maintaining another sysroot is basically dealing with another complete isolated system, and I believe we have tools that automate these, since it's just a container; and some of those tools can work without root privileges, e.g. bwrap. Or simply unshare and call systemd-nspawn. But this approach is going to take more space since all dependencies would be installed twice, and depending on OP's resources this may be too much.

On Fri, Aug 18, 2023 at 04:50:27 +0200, mpan wrote:

...

my system partition is as good as full Other than that, see the extra/ncdu package. Run it as sudo in read-only mode (for safety) to find the biggest offenders:

sudo ncdu -xr

If space is really that tight, you can accomplish almost the same thing (it's just not interactive) with something like $ du -hs * | sort -h This will list the usage of each item in the current directory, with sizes in human-friendly units, sorted ascending by size. It'll generally not be surprising where the biggest directories are, but just how much these directories use can still be surprising. I hope this helps! -- Cheers, Luna Celeste

On Fri, 2023-08-18 at 09:17 +0100, pete wrote:

https://browse-tutorials.com/tutorial/arch-linux-move-root-partition-hdd-ssd

Hi Pete, consider to change cp -a /mnt/hdd_mount/* /mnt/ssd_mount/ to cp -Tai /mnt/hdd_mount/ /mnt/ssd_mount/ Why? -T just in case a source mount point should contain hidden files -i because you never know ;) Regards, Ralf