public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Robin Roevens <robin.roevens@disroot.org>
To: development@lists.ipfire.org
Subject: Re: [PATCH 0/2] buildprocess: additional pak metadata
Date: Thu, 12 Aug 2021 17:34:19 +0200	[thread overview]
Message-ID: <3ea3988517b265a62cc91f6a0382e50b0e465fcb.camel@disroot.org> (raw)
In-Reply-To: <20210701191514.8176-1-robin.roevens@disroot.org>

[-- Attachment #1: Type: text/plain, Size: 2450 bytes --]

Hi all

Had anybody already had a chance to start reviewing this patch-set
during my absence ?

I also have changes to Pakfire in the pipeline to actually use the
metadata provided by this set, but I'm waiting to submit those patches
as they depend on the acceptance of this set (and on my
other patch "pakfire: implement function to parse meta files" to counter Jonathan's comments about de pakfire code quality which I originally duplicated in a previous prototype of the changes to come.)

Regards

Robin

Robin Roevens schreef op do 01-07-2021 om 21:15 [+0200]:
> Hi
> 
> Second attemt to submit this patchset. Hoping the mailserver won't
> find
> malicious URLs in it.
> 
> For completeness, the summary included in the first attempt:
> 
> As discussed earlier, I hereby submit a patchset adding extra
> metadata 
> to all pak's.
> 
> First patch adds the new metadata fields "Summary" and "Services" to
> the 
> meta-file templates and introduces the new macro INSTALL_INITSCRIPTS 
> accepting a space seperated list of initscripts to install to avoid
> duplicating the list of service initscripts. (Once in the new
> SERVICES
> meta-data field and once by calling INSTALL_INITSCRIPT for each of 
> them).
> The original INSTALL_INITSCRIPT macro is kept (and called by the new
> macro) for corner cases where non-service initscripts need to be 
> installed and for use by non-pak lfs files as they currently don't
> have 
> a SERVICES variable. 
> 
> The second patch adds the new metadata for all pak's in their
> respective
> lfs files. 
> As I went over all pak lfs files, I did not encounter any corner
> cases
> hence all calls to INSTALL_INITSCRIPT are replaced by calls to the
> new
> INSTALL_INITSCRIPTS passing the SERVICES variable as argument.
> The only special case maybe worth mentioning is Icinga, where a
> service
> initscript is installed by a make rule of the source. Hence no call
> to
> INSTALL_INITSCRIPT or INSTALL_INITSCRIPTS is required. But the
> service
> is included in the SERVICES variable to have it recorded in the meta-
> file.
> 
> This set does not yet contain changes in pakfire or services.cgi to
> actually do something with the new meta-data.
> Those changes will be posted shortly.
> 
> Regards
> 
> Robin
> 
> 
> 


-- 
Dit bericht is gescanned op virussen en andere gevaarlijke
inhoud door MailScanner en lijkt schoon te zijn.


  parent reply	other threads:[~2021-08-12 15:34 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-01 19:15 Robin Roevens
2021-07-01 19:15 ` [PATCH 1/2] buildprocess: Add extra metadata to meta-* files Robin Roevens
2021-07-01 19:15 ` [PATCH 2/2] buildprocess: Add extra metadata to pak lfs files Robin Roevens
2021-08-12 15:34 ` Robin Roevens [this message]
2021-08-12 15:37   ` [PATCH 0/2] buildprocess: additional pak metadata Michael Tremer
2021-08-12 18:28     ` Robin Roevens
2021-08-13  9:18       ` Michael Tremer
2021-08-13 10:49         ` Robin Roevens
2021-08-13 11:19           ` Michael Tremer
     [not found] <1b25db163f59f5f89796a05b7d97ab2098eb230d.camel@disroot.org>
2021-07-01  8:31 ` Michael Tremer
2021-07-01 19:31   ` Robin Roevens
  -- strict thread matches above, loose matches on Subject: below --
2021-06-24 22:50 Robin Roevens
2021-06-24 23:04 ` Robin Roevens
2021-06-26 12:09   ` 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=3ea3988517b265a62cc91f6a0382e50b0e465fcb.camel@disroot.org \
    --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