From: Frederick Reeve <frederick@woodland-i.org>
To: Sven Vermeulen <sven.vermeulen@rug.ac.be>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] net.eth0
Date: 09 Mar 2003 10:58:53 +0100 [thread overview]
Message-ID: <1047203933.6575.6.camel@localhost.localdomain> (raw)
In-Reply-To: <20030309104118.GB1765@Daikan.pandora.be>
> Isn't the --nodeps options that what you are looking for?
>
> --nodeps (-O short option)
> Merge specified packages, but don't merge any dependencies.
> Note that the build may fail if deps aren't satisfied.
>
No nodeps doesn't ignore the fact a package is masked allowing a merge
of a package that is masked. Many masked packages will install and
correctly especially when you are talking about whats masked out for
alpha. a force option would allow users to easily test the masked out
packages for themselves (without changing there package.mask file) and
they in return could give you reports.
Frederick <sabin>
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2003-03-09 18:03 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-08 20:46 [gentoo-dev] net.eth0 Frederick Reeve
2003-03-09 5:16 ` Martin Schlemmer
[not found] ` <20030309070831.GB23088@purematrix.com>
2003-03-09 10:02 ` Frederick Reeve
2003-03-09 22:58 ` Joseph Carter
2003-03-17 15:35 ` Wout Mertens
2003-03-18 3:09 ` Joseph Carter
2003-03-18 18:44 ` Martin Schlemmer
[not found] ` <Pine.GSO.4.53.0303191423140.15485@oaktree.cisco.com>
2003-03-21 6:43 ` Martin Schlemmer
2003-03-21 15:42 ` Wout Mertens
2003-03-21 15:44 ` Paul de Vrieze
2003-03-21 23:03 ` Martin Schlemmer
2003-03-22 2:07 ` Nick Matthews
2003-03-09 10:41 ` Sven Vermeulen
2003-03-09 9:58 ` Frederick Reeve [this message]
2003-03-10 6:44 ` Sven Vermeulen
-- strict thread matches above, loose matches on Subject: below --
2003-03-19 17:16 Wout Mertens
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=1047203933.6575.6.camel@localhost.localdomain \
--to=frederick@woodland-i.org \
--cc=gentoo-dev@gentoo.org \
--cc=sven.vermeulen@rug.ac.be \
/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