unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Simon Tournier <zimon.toutoune@gmail.com>
To: "(" <paren@disroot.org>, Vagrant Cascadian <vagrant@debian.org>,
	Gary Johnson <lambdatronic@disroot.org>,
	Rodrigo Morales <moralesrodrigo1100@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: Newbie user: Feedback on custom package definition
Date: Tue, 07 Mar 2023 14:41:15 +0100	[thread overview]
Message-ID: <865ybcbrwk.fsf@gmail.com> (raw)
In-Reply-To: <CQW5V16LWFCV.G3E2L8MGSWBT@guix-framework>

Hi,

On Thu, 02 Mar 2023 at 19:57, "(" <paren@disroot.org> wrote:
> On Thu Mar 2, 2023 at 6:54 PM GMT, Vagrant Cascadian wrote:
>> I often wonder if the name "trivial-build-system" should not be
>> something more like:
>>
>>   diy-get-your-hands-messy-with-a-lot-of-effort-build-system
>
> Maybe PRIMITIVE-BUILD-SYSTEM?

Well, I am not convinced that we should change the name.  It is there
since some many years. :-)

However, we could improve the manual.  For instance, it reads [1] «A
notable exception is the “bare-bones” trivial-build-system (see Build
Systems).»

Then under “Build System“ section [2], this “bare-bones” could be more
explicit.  For example, extend a bit its documentation [3].

Well, it will mitigate a bit the common “trap” about the most
non trivial build system. :-)

1: <https://guix.gnu.org/manual/devel/en/guix.html#Build-Phases>
2: <https://guix.gnu.org/manual/devel/en/guix.html#Build-Systems>
3: <https://guix.gnu.org/manual/devel/en/guix.html#index-trivial_002dbuild_002dsystem>


Cheers,
simon



      reply	other threads:[~2023-03-07 13:49 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-28 22:06 Newbie user: Feedback on custom package definition Rodrigo Morales
2023-03-01  1:12 ` 宋文武
2023-03-02 15:10 ` Gary Johnson
2023-03-02 18:54   ` Vagrant Cascadian
2023-03-02 19:57     ` (
2023-03-07 13:41       ` Simon Tournier [this message]

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=865ybcbrwk.fsf@gmail.com \
    --to=zimon.toutoune@gmail.com \
    --cc=help-guix@gnu.org \
    --cc=lambdatronic@disroot.org \
    --cc=moralesrodrigo1100@gmail.com \
    --cc=paren@disroot.org \
    --cc=vagrant@debian.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 read-only IMAP folder(s) and NNTP newsgroup(s).