From: Vagrant Cascadian <vagrant@debian.org>
To: 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: Thu, 02 Mar 2023 10:54:41 -0800 [thread overview]
Message-ID: <87a60v2dce.fsf@yucca> (raw)
In-Reply-To: <87sfen9nma.fsf@disroot.org>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
On 2023-03-02, Gary Johnson wrote:
> Rodrigo Morales <moralesrodrigo1100@gmail.com> writes:
>> 3 The questions
>> ===============
>>
>> + What changes would you do to improve the definition of the package
>> that I wrote?
>
> Whenever possible, you should not be using the `trivial-build-system`.
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
I think the word "trivial" implies to people that it should be easy to
use with trivial packaging tasks, when in fact, the build system does so
little that you actually have to do a lot of work to get it to generate
a proper package... I certainly fell down that trap when I first started
working on some packages...
live well,
vagrant
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2023-03-02 18:55 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 [this message]
2023-03-02 19:57 ` (
2023-03-07 13:41 ` Simon Tournier
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=87a60v2dce.fsf@yucca \
--to=vagrant@debian.org \
--cc=help-guix@gnu.org \
--cc=lambdatronic@disroot.org \
--cc=moralesrodrigo1100@gmail.com \
/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).