public inbox for gentoo-dev@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Cc: jonas.licht@fem.tu-ilmenau.de, nex+b-g-o@nexadn.de
Subject: Re: [gentoo-dev] [RFC] www-nginx/ category and nginx-module.eclass for nginx modules
Date: Tue, 24 Jan 2023 18:11:27 +0100	[thread overview]
Message-ID: <b4277a06af7e76539e00396cba2e24b78642d03d.camel@gentoo.org> (raw)
In-Reply-To: <20230124155156.12178-1-nex@nexadn.de>

On Tue, 2023-01-24 at 16:51 +0100, Adrian Schollmeyer wrote:
> Hey there,
> 
> a while back Jonas Licht (Cc) wrote an eclass for Nginx dynamic modules.
> For a few years now, Nginx supports building third party dynamic modules
> outside of the Nginx source tree with the help of Nginx's build system.
> Since this involves quite some work to obtain information from the Nginx
> build configuration and using Nginx's build system to actually build the
> module, an eclass was written. The last RFC didn't make it into
> ::gentoo, since the requested changes haven't been applied.
> 
> However, we have been working on the eclass again and applied all the
> requested changes, made it EAPI=8 compatible and were able to use it
> successfully to package a third party Nginx module in ::fem-overlay [0].
> 
> This patchset contains the reworked nginx-module.eclass for building
> third party modules using Nginx's build system as separate packages.
> Furthermore the category www-nginx is added where these third party
> modules shall be put. Lastly, www-nginx/nginx-vod-module is added as a
> first package using this eclass.
> 
> The patchset is also available as PR #16053 on GitHub [1]. If this
> patchset is applied, the other PR for adding nginx-vod-module [2]
> probably becomes obsolete [2].
> 

How many packages do you expect to add to this new category?  It's not
customary to create a new category for one package.

-- 
Best regards,
Michał Górny



  parent reply	other threads:[~2023-01-24 17:11 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 15:51 [gentoo-dev] [RFC] www-nginx/ category and nginx-module.eclass for nginx modules Adrian Schollmeyer
2023-01-24 15:51 ` [gentoo-dev] [PATCH v3 1/3] profiles/categories: add www-nginx Adrian Schollmeyer
2023-01-24 15:51 ` [gentoo-dev] [PATCH v3 2/3] Add nginx-module.eclass Adrian Schollmeyer
2023-01-24 15:51 ` [gentoo-dev] [PATCH v3 3/3] www-nginx/nginx-vod-module: add new package Adrian Schollmeyer
2023-01-24 17:11 ` Michał Górny [this message]
2023-01-24 18:53   ` [gentoo-dev] [RFC] www-nginx/ category and nginx-module.eclass for nginx modules Anna (cybertailor) Vyalkova
2023-01-24 19:01   ` Adrian Schollmeyer

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=b4277a06af7e76539e00396cba2e24b78642d03d.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev@lists.gentoo.org \
    --cc=jonas.licht@fem.tu-ilmenau.de \
    --cc=nex+b-g-o@nexadn.de \
    /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