From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Making testing easier in IPFire 2
Date: Tue, 11 Feb 2020 14:28:45 +0000 [thread overview]
Message-ID: <20200211142853.8561-1-michael.tremer@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 538 bytes --]
This patchset makes testing easier in IPFire 2.
Since we are now trying to use the nightly builds more, pakfire is now
automatically configured to use the packages from the correct tree.
That means that testing add-ons will be easier without any manual
changes of any configuration files. Yay.
Additionally, there is now a dropdown on the pakfire page where
users can change from one tree to another one which makes testing
core updates easier, too.
Please review my changes and let me know if I messed anything up.
Best,
-Michael
next reply other threads:[~2020-02-11 14:28 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-11 14:28 Michael Tremer [this message]
2020-02-11 14:28 ` [PATCH 1/8] pakfire: Automatically compose $version Michael Tremer
2020-02-11 14:28 ` [PATCH 2/8] pakfire.cgi: Remove some old settings Michael Tremer
2020-02-11 14:28 ` [PATCH 3/8] pakfire.cgi: Rename %pakfiresettings to %cgiparams Michael Tremer
2020-02-11 14:28 ` [PATCH 4/8] pakfire.cgi: Add UI to select repository Michael Tremer
2020-02-11 14:28 ` [PATCH 5/8] pakfire: Add version suffix when in a certain tree Michael Tremer
2020-02-11 14:28 ` [PATCH 6/8] make.sh: Tidy up Git commands Michael Tremer
2020-02-11 14:28 ` [PATCH 7/8] make.sh: Cleanup code that builds ${SYSTEM_RELEASE} Michael Tremer
2020-02-11 14:28 ` [PATCH 8/8] make.sh: Configure Pakfire to load packages from the correct tree Michael Tremer
2020-02-12 13:49 ` Making testing easier in IPFire 2 Stefan Schantl
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=20200211142853.8561-1-michael.tremer@ipfire.org \
--to=michael.tremer@ipfire.org \
--cc=development@lists.ipfire.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