From: Robin Roevens <robin.roevens@disroot.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH v2 00/10] pakfire: remove dup. code + seperate ui/logic
Date: Fri, 29 Jul 2022 22:11:51 +0200 [thread overview]
Message-ID: <191b0caddbf3676709f8c1bdf296e771766f9631.camel@sicho.home> (raw)
In-Reply-To: <b7ced57f-8467-6150-57ff-ab5975fad9b6@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 4979 bytes --]
Hi Peter
Peter Müller schreef op do 28-07-2022 om 13:51 [+0000]:
> Hello Robin,
>
> thanks for your mail, the second version of this patchset, and
> marking the first
> version as "superseded" in Patchwork. :-)
>
> I just merged the patchset into "next", so everyone running on the
> "unstable" tree
> can see the changes and test them. Commit
> 3543c24f41027c6e4437b8d1b3d3ca75d47ed3c9
> should ship all the files you changed, please let me know in case I
> forgot anything.
I think, aside from de localization files, you have them all. I'm not
completely sure what this rootfile is you modified here? Are those all
files that differ since last core update ? But I asume lang files are
then handled somewhere else ?
Robin
>
> All the best,
> Peter Müller
>
>
> > Hi all
> >
> > As promised a revision of this patchset by the end of July.
> > Also fixing bug #12868, both in patch 01 (installed: yes/no output)
> > and
> > patch 06 (don't trow error on valid '--no-color' option).
> >
> > This is quite a large patchset on delicate code which was discussed
> > upon
> > previous submission, but that was almost half a year ago. So I will
> > try
> > to link references to discussions on my previous submission where
> > appropriate to refresh some memories :-).
> >
> > What was changed since last submission; implementing/fixing
> > Michael's remarks/concerns:
> > - Patch 01: Added translations as requested here:
> >
> > https://lists.ipfire.org/pipermail/development/2022-March/012782.html
> > - Patch 02: New patch translating WUI header/footer text
> > - Patch 03: (previously patch 02) was not changed
> > - Patch 04: (previously patch 03) replaced a forgotten
> > fetchfile/move
> > combo by new getmetafile function
> > - Previous patch 04 was removed as the function
> > coreupdate_available turned out no
> > longer used.
> > See:
> > https://lists.ipfire.org/pipermail/development/2022-March/012884.html
> > - Patch 05: Replaced seq shell command by perl seq-method,
> > consistent
> > use of 'Core-Update' as requested here:
> >
> > https://lists.ipfire.org/pipermail/development/2022-March/012787.html
> > - Patch 06: Added exitcode to pakfire list as requested here:
> >
> > https://lists.ipfire.org/pipermail/development/2022-March/012787.html
> > Also exit with error when an unknown parameter is
> > passed to
> > pakfire list
> > Added a small fix (in my opinion): log termination of
> > pakfire
> > inside END block
> > - Patch 07: Removed function coreupdate_available as it was
> > concluded
> > that it was no longer needed (see again:
> >
> > https://lists.ipfire.org/pipermail/development/2022-March/012884.html
> > )
> > Added meaningfull status exit code as remarked here:
> >
> > https://lists.ipfire.org/pipermail/development/2022-March/012788.html
> > Split previous patch 07 pakfire.cgi changes in new
> > patch 08:
> > - Patch 08: New patch, previously part of patch 07
> > Fixed localization as pointed out here:
> >
> > https://lists.ipfire.org/pipermail/development/2022-March/012788.html
> > - Patch 09: (previously patch 08) Split previous patch 08 into
> > patch 09
> > adding 'getmetadata' function and 'pakfire info' and
> > patch 10
> > implementing the new 'getmetadata' in service.cgi.
> > Show clean warning message when no packages are found
> > with requested pakfire list filter
> > - Patch 10: (previously part of patch 08) Removed hardcoded
> > exclusions
> > in services.cgi as pointed out here:
> >
> > https://lists.ipfire.org/pipermail/development/2022-March/012789.html
> > Previous patch 09 was dropped from this patchset as there turned
> > out to
> > be major problems with it and should be rethinked as pointed out
> > here:
> > https://lists.ipfire.org/pipermail/development/2022-March/012856.html
> >
> >
> >
> > I think I have tested this all throughly but as these are quite
> > interusive
> > changes to the pakfire core workings; Please do not trust my
> > testing and test
> > these patches yourselves during review. I would not want to carry
> > the
> > responibilities of breaking pakfire alone :-)
> >
> > Regards
> > Robin
> >
> >
> >
> >
>
--
Dit bericht is gescanned op virussen en andere gevaarlijke
inhoud door MailScanner en lijkt schoon te zijn.
next prev parent reply other threads:[~2022-07-29 20:11 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-28 11:21 Robin Roevens
2022-07-28 11:21 ` [PATCH v2 01/10] pakfire: Refactor dblist seperating UI and logic Robin Roevens
2022-07-28 11:21 ` [PATCH v2 02/10] pakfire: Translate WUI header/footer text Robin Roevens
2022-07-28 11:21 ` [PATCH v2 03/10] pakfire: Replace duplicate code with dblist functioncall Robin Roevens
2022-07-28 11:21 ` [PATCH v2 04/10] pakfire: Replace dbgetlist duplicate code Robin Roevens
2022-07-28 11:21 ` [PATCH v2 05/10] pakfire: Optimize upgradecore function Robin Roevens
2022-07-28 11:21 ` [PATCH v2 06/10] pakfire: Add list upgrade functionality Robin Roevens
2022-07-28 11:21 ` [PATCH v2 07/10] pakfire: Refactor status seperating UI and logic Robin Roevens
2022-07-28 11:21 ` [PATCH v2 08/10] pakfire: Replace status duplicate code Robin Roevens
2022-07-28 11:21 ` [PATCH v2 09/10] pakfire: Add getmetadata function Robin Roevens
2022-07-28 11:21 ` [PATCH v2 10/10] pakfire: Replace getmetadata duplicate code Robin Roevens
2022-07-28 13:51 ` [PATCH v2 00/10] pakfire: remove dup. code + seperate ui/logic Peter Müller
2022-07-29 20:11 ` Robin Roevens [this message]
2022-07-28 19:43 ` Michael Tremer
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=191b0caddbf3676709f8c1bdf296e771766f9631.camel@sicho.home \
--to=robin.roevens@disroot.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