From: jingai <jingai@floatingpenguins.com>
To: linuxppc-dev@lists.linuxppc.org
Subject: YUP and RPM dependencies
Date: Fri, 17 Mar 2000 20:22:17 EST [thread overview]
Message-ID: <200003180622.BAA20354@shell.faradic.net> (raw)
After I heard about the YellowDog Update Program (YUP) from someone on this
list, I went and downloaded the RPM and installed it. However, it
initially performs some sanity checks, such as making sure all installed
RPMS pass dependency checks, and will not continue if this fails.. but I've
got a few RPMS (such as glibc, which requires the kernel-headers RPMS, but
I build my own kernel from sources) that I purposely installed even though
they fail dependency checks..
.so, my question is, is there a way to bypass this check (a force option
or somesuch)? And if not, if anyone from the YD team is here, please make
this an option.
But, as a side note, I'm ecstatic that this sort of app is finally out.. I
was just about to suck down the Debian install CDs, if for nothing other
than it's automatic package updater..
-j
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next reply other threads:[~2000-03-18 1:22 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-03-18 1:22 jingai [this message]
2000-03-18 7:14 ` YUP and RPM dependencies Gabriel Paubert
2000-03-18 9:53 ` Wolfgang Denk
2000-03-18 20:05 ` Dan Burcaw
2000-03-20 16:55 ` Stephen Edie
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=200003180622.BAA20354@shell.faradic.net \
--to=jingai@floatingpenguins.com \
--cc=linuxppc-dev@lists.linuxppc.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;
as well as URLs for NNTP newsgroup(s).