public inbox for gentoo-dev-announce@lists.gentoo.org
 help / color / mirror / Atom feed
From: "Michał Górny" <mgorny@gentoo.org>
To: gentoo-dev-announce <gentoo-dev-announce@lists.gentoo.org>
Cc: gentoo-dev <gentoo-dev@lists.gentoo.org>
Subject: [gentoo-dev-announce] Eclass up for grabs: bsdmk.eclass
Date: Sat, 12 Oct 2019 14:12:17 +0200	[thread overview]
Message-ID: <816938b708b4960228406c11755ce93e37bad4ad.camel@gentoo.org> (raw)

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

Hi,

bsdmk.eclass needs a new maintainer.

This eclass is generally used by packages taken from *BSD source tree,
and that need *BSD make + some fancy rules to build.

The current consumers are:

dev-libs/libexecinfo
eclass/freebsd.eclass
net-firewall/pftop
sys-libs/netbsd-csu
sys-process/pidof-bsd

All but netbsd-csu are past last rites.  The latter is also mostly
obsoleted by new compiler-rt versions, so it may disappear at some point
in the future.

-- 
Best regards,
Michał Górny


[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 618 bytes --]

                 reply	other threads:[~2019-10-12 12:16 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=816938b708b4960228406c11755ce93e37bad4ad.camel@gentoo.org \
    --to=mgorny@gentoo.org \
    --cc=gentoo-dev-announce@lists.gentoo.org \
    --cc=gentoo-dev@lists.gentoo.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