From: Vinicius Monego <monego@posteo.net>
To: pinoaffe <pinoaffe@gmail.com>
Cc: 66199@debbugs.gnu.org
Subject: [bug#66199] [PATCH] gnu: librepcb: Update to 1.0.0.
Date: Wed, 27 Sep 2023 00:35:14 +0000 [thread overview]
Message-ID: <cb1f573c-0681-d9e3-6faa-3d0c1e30667e@posteo.net> (raw)
In-Reply-To: <87h6nhdtbh.fsf@gmail.com>
Em 26/09/2023 09:08, pinoaffe escreveu:
> Hi,
Hi!
> thank you for your review!
>
> Vinicius Monego <monego@posteo.net> writes:
>> The commit message should also mention the switch to
>> cmake-build-system, the "not overriding" of the configure phase, the
>> new inputs and the test skip..
> I wasn't sure how to phrase / format this, is what I arrived at OK?
You can check the logs of e.g. commit
19617735df2b1af3b169d8153ae543ad3e0fc1a1 for reference.
>> Inputs should be sorted alphabetically.
> Done
>
'googletest' should be a native input, it's a test requirement only.
[...]
> I'll send some updated patches in a minute
>
> Kind regards,
> pinoaffe
[Comment on the LibrePCB update patch specifically]: This v2 is much
better, thanks. While investigating the build I also found a few more
things that could be improved:
- The bundles that were unvendored can be deleted in a source snippet
(see e.g. the mixxx package).
- LibrePCB builds a test executable at
tests/unittests/librepcb-unittests. Instead of 'make test', that file
could be run manually when overriding the check phase.
- The license list should be updated as some of the bundles listed there
are not being provided anymore, or even better let it be only gpl3+
because that's the license of the final product.
- I got two merge conflicts on 06dc36ffb7cde821a4762b299d1c95b3788ba110,
please rebase it to the latest commit.
If the tests are too problematic that's fine, I can merge this patch
with the other changes later this week.
Vinicius
next prev parent reply other threads:[~2023-09-27 0:36 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-25 20:27 [bug#66199] [PATCH] gnu: librepcb: Update to 1.0.0 pinoaffe
2023-09-26 0:37 ` Vinicius Monego
2023-09-26 12:08 ` pinoaffe
2023-09-27 0:35 ` Vinicius Monego [this message]
2023-09-27 16:06 ` pinoaffe
2023-09-26 12:16 ` [bug#66199] [PATCH v2 1/2] gnu: Add fontobene-qt5 pinoaffe
2023-09-26 12:16 ` [bug#66199] [PATCH v2 2/2] gnu: librepcb: Update to 1.0.0 pinoaffe
2023-09-27 0:39 ` [bug#66199] [PATCH v2 1/2] gnu: Add fontobene-qt5 Vinicius Monego
2023-09-27 16:11 ` pinoaffe
2023-09-27 16:14 ` [bug#66199] [PATCH v3 " pinoaffe
2023-09-27 16:14 ` [bug#66199] [PATCH v3 2/2] gnu: librepcb: Update to 1.0.0 pinoaffe
2023-09-27 18:45 ` pinoaffe
2023-09-27 18:46 ` [bug#66199] [PATCH v4 1/2] gnu: Add fontobene-qt5 pinoaffe
2023-09-27 18:46 ` [bug#66199] [PATCH v4 2/2] gnu: librepcb: Update to 1.0.0 pinoaffe
2023-09-30 1:34 ` Vinicius Monego
2023-10-03 23:39 ` pinoaffe
2023-10-07 1:16 ` bug#66199: " Vinicius Monego
2023-10-04 0:15 ` [bug#66199] [PATCH v5 1/2] gnu: Add fontobene-qt5 pinoaffe
2023-10-04 0:15 ` [bug#66199] [PATCH v5 2/2] gnu: librepcb: Update to 1.0.0 pinoaffe
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=cb1f573c-0681-d9e3-6faa-3d0c1e30667e@posteo.net \
--to=monego@posteo.net \
--cc=66199@debbugs.gnu.org \
--cc=pinoaffe@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
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).