From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=none autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 2661 invoked from network); 20 Oct 2021 11:45:34 -0000 Received: from 4ess.inri.net (216.126.196.42) by inbox.vuxu.org with ESMTPUTF8; 20 Oct 2021 11:45:34 -0000 Received: from oat.nine.sirjofri.de ([5.45.105.127]) by 4ess; Wed Oct 20 07:38:12 -0400 2021 Received: from sirjofri.de ([95.90.219.31]) by oat; Wed Oct 20 13:38:02 +0200 2021 Date: Wed, 20 Oct 2021 11:38:01 +0000 (UTC) From: sirjofri To: Stuart Morrow <9front@9front.org> Message-ID: In-Reply-To: References: MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-Correlation-ID: List-ID: <9front.9front.org> List-Help: X-Glyph: ➈ X-Bullshit: RESTful advanced module content-driven-oriented map/reduce layer Subject: Re: [9front] installing things system-wide vs for user Reply-To: 9front@9front.org Precedence: bulk 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 : > Does anyone use a strict way of deciding which to do for a given thing > you're installing?