From: Bartosch Pixa <darkspecter@gentoo.org>
To: Gentoo Dev Mailing List <gentoo-dev@gentoo.org>
Subject: Re: [gentoo-dev] DEVS: depedency checking for other arches
Date: 09 Jul 2003 16:01:08 +0200 [thread overview]
Message-ID: <1057759267.11361.1.camel@chloe> (raw)
In-Reply-To: <Pine.LNX.4.53.0307090845140.31115@stargazer.weeve.org>
[-- Attachment #1: Type: text/plain, Size: 722 bytes --]
On Wed, 2003-07-09 at 15:00, Weeve wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> Hi all,
>
> Just a request/plea to developers in regards to adding/adjusting
> dependencies on ebuilds that have multiple arch keywords (i.e. x86, ppc,
> sparc, mips, etc). When a dependency is added or adjusted for an existing
> ebuild, particularly ones that have multiple arch keywords, please please
> please check to see if those dependencies can be built for all other
> arches for the same tree the ebuild you are working on is currently marked
> for (stable or unstable).
i couldn't agree more :)
regards
--
Bartosch Pixa
Gentoo Linux Developer http://www.gentoo.org
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2003-07-09 14:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-07-09 13:00 [gentoo-dev] DEVS: depedency checking for other arches Weeve
2003-07-09 14:01 ` Bartosch Pixa [this message]
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=1057759267.11361.1.camel@chloe \
--to=darkspecter@gentoo.org \
--cc=gentoo-dev@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