From: Joshua Kinard <kumba@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] virtual/sctp to choose the right SCTP lib for Linux/FreeBSD?
Date: Sun, 06 Apr 2014 16:57:10 -0400 [thread overview]
Message-ID: <5341BFA6.6010306@gentoo.org> (raw)
In-Reply-To: <5341B3CA.3060408@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 2160 bytes --]
On 04/06/2014 16:06, Joshua Kinard wrote:
> On 04/06/2014 04:49, Ulrich Mueller wrote:
>>>>>>> On Sat, 05 Apr 2014, Joshua Kinard wrote:
>>
>>> I've attached a first draft of virtual/sctp/sctp-0.ebuild, which
>>> passes repoman checks, but I think it needs to be made
>>> multilib-aware. Additionally, that means lksctp-tools probably needs
>>> some multilib-magic applied. I am not finding a solid guide on
>>> properly upgrading an ebuild to become multilib-aware. Can one of
>>> the multilib experts check things and let me know what is needed if
>>> people agree this is a good way to go down?
>>
>> This doesn't answer your multilib question, but I believe that
>> kernel_* is not needed in IUSE:
>>
>>> IUSE="kernel_linux kernel_FreeBSD static-libs"
>>
>> KERNEL is both in USE_EXPAND and USE_EXPAND_IMPLICIT of
>> profiles/base/make.defaults, therefore it's implicit in EAPI 5.
>
> Thanks, I removed those and IUSE as well, since it's empty.
>
>
>> I'd also omit all empty variable assignments (like HOMEPAGE=""),
>> they are no longer necessary.
>
> I derived this ebuild from virtual/udev's (as the leftover comment implied).
> Someone might want to remove the empty vars there as well. Perhaps repoman
> should check for empty vars like HOMEPAGE/SRC_URI/IUSE and flag as a warning?
>
Derp, since this is a virtual for a linkable library, set DEPEND first, then
RDEPEND to ${DEPEND}.
While FBSD is the only other official non-Linux port (I think OBSD/NBSD are
still only in Prefix?), should REQUIRED_USE be set to limit this virtual to
kernel_linux and kernel_FreeBSD?
Hmm, and further thinking, if we had a kFreeBSD variant, things would get
more interesting. Someone would probably have to abstract the SCTP lib code
out of freebsd-lib to work in that environment, since everything would be
running on top of a glibc userland. I wonder if Debian's run into that yet...
--
Joshua Kinard
Gentoo/MIPS
kumba@gentoo.org
4096R/D25D95E3 2011-03-28
"The past tempts us, the present confuses us, the future frightens us. And
our lives slip away, moment by moment, lost in that vast, terrible in-between."
--Emperor Turhan, Centauri Republic
[-- Attachment #2: sctp-0.ebuild --]
[-- Type: text/plain, Size: 465 bytes --]
# Copyright 1999-2014 Gentoo Foundation
# Distributed under the terms of the GNU General Public License v2
# $Header: $
EAPI=5
DESCRIPTION="Virtual to select net-misc/lksctp-tools or sys-freebsd/freebsd-lib for userland SCTP lib support"
SLOT="0"
KEYWORDS="~alpha ~amd64 ~mips ~ppc ~ppc64 ~sparc ~x86 ~amd64-fbsd ~sparc-fbsd ~x86-fbsd"
DEPEND="|| (
kernel_linux? ( net-misc/lksctp-tools )
kernel_FreeBSD? ( sys-freebsd/freebsd-lib )
)"
RDEPEND="${DEPEND}"
next prev parent reply other threads:[~2014-04-06 20:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-06 0:23 [gentoo-dev] virtual/sctp to choose the right SCTP lib for Linux/FreeBSD? Joshua Kinard
2014-04-06 8:49 ` Ulrich Mueller
2014-04-06 20:06 ` Joshua Kinard
2014-04-06 20:57 ` Joshua Kinard [this message]
2014-04-06 21:05 ` Ulrich Mueller
2014-04-08 7:21 ` Joshua Kinard
2014-04-06 21:00 ` Ulrich Mueller
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=5341BFA6.6010306@gentoo.org \
--to=kumba@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