From: sirjofri <sirjofri+ml-9front@sirjofri.de>
To: Stuart Morrow <9front@9front.org>
Subject: Re: [9front] installing things system-wide vs for user
Date: Wed, 20 Oct 2021 11:38:01 +0000 (UTC) [thread overview]
Message-ID: <b4658f64-5229-4898-8609-868a217f3fad@sirjofri.de> (raw)
In-Reply-To: <CABB-WO_2QFOvQnz-AZR_1yYd7JMLrdtHaHx1UgfS8nacdwmBOg@mail.gmail.com>
Here's what I usually do:
I store repositories for system-wide applications in glenda user
directory (/usr/glenda/src). mk install usually puts the files in
/$objtype/bin etc, which is fine.
User-based apps I personally do like this: $home/src for repositories, mk
install should install to $home/bin/$objtype. Often enough
BIN=$home/bin/$objtype is enough there.
I try to keep /sys as clean as possible, with only occasional manual
patches applied (eg smtp.c).
sirjofri
20.10.2021 12:48:22 Stuart Morrow <morrow.stuart@gmail.com>:
> Does anyone use a strict way of deciding which to do for a given thing
> you're installing?
next prev parent reply other threads:[~2021-10-20 11:45 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-20 10:48 Stuart Morrow
2021-10-20 11:38 ` sirjofri [this message]
2021-10-21 0:18 ` Pavel Renev
2021-10-21 5:51 ` sirjofri
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4658f64-5229-4898-8609-868a217f3fad@sirjofri.de \
--to=sirjofri+ml-9front@sirjofri.de \
--cc=9front@9front.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).