From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: debianutils: system worthy ?
Date: Tue, 29 Jan 2008 09:26:12 +0000 (UTC) [thread overview]
Message-ID: <pan.2008.01.29.09.26.12@cox.net> (raw)
In-Reply-To: 479E0BB2.3020102@gentoo.org
Jan Kundrát <jkt@gentoo.org> posted 479E0BB2.3020102@gentoo.org, excerpted
below, on Mon, 28 Jan 2008 18:06:58 +0100:
> Duncan wrote:
>> Mainstream kernel's default make install uses /sbin/installkernel if it
>> exists, so I've been using it, invoking the kernel's make install from
>> my own kernel scripts. installkernel invokes mkboot...
>
> We (the docs team) have never suggested out users to run `make install`
> for various reasons, see bug 183346 (and the linked gentoo-doc thread)
> for details.
Thanks. I sort of knew that, but some of us first got comfortable
installing kernels on other distributions, and brought our scripts and
habits with us, changing them only enough to work in their new habitat.
=8^)
Here, I've never used the Gentoo kernel packages, simply because I've
never needed to, because I already had a system that worked for me --
downloading, verifying, configuring, compiling and installing the kernel
direct off of kernel.org, with my own site-specific patches. There's
probably a significant number of others doing similar things, and if I
were to guess, I'd say a fair share of those that do are probably running
professional and therefore production systems, simply because that's the
sort that's likely to /have/ such customized solutions -- likely in some
cases even designed specifically so the same scripts can be used on
multiple distributions.
As caster pointed out, however, just removing the package from system
doesn't unmerge it, and if people run --depclean without --ask or --
pretend first, well... Maybe they'll learn to do so, next time! =8^)
So yeah, I'd say a warning is warranted, but after that just do it.
Surely some will complain, but it's not like we can be there constantly
holding their hands. Gentoo makes a very deliberate point of expecting
its users to be grownups in that way, and I'm glad it does! =8^)
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
--
gentoo-dev@lists.gentoo.org mailing list
next prev parent reply other threads:[~2008-01-29 9:26 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-28 12:23 [gentoo-dev] debianutils: system worthy ? Mike Frysinger
2008-01-28 12:32 ` Rémi Cardona
2008-01-28 13:11 ` Fabian Groffen
2008-01-28 14:40 ` [gentoo-dev] " Duncan
2008-01-28 17:06 ` Jan Kundrát
2008-01-29 9:26 ` Duncan [this message]
2008-01-28 17:20 ` Vlastimil Babka
2008-01-29 9:06 ` Duncan
2008-01-28 14:57 ` [gentoo-dev] " Doug Klima
2008-01-28 15:35 ` Yuri Vasilevski
2008-01-28 16:37 ` Petteri Räty
2008-01-28 17:43 ` Krzysiek Pawlik
2008-01-28 17:59 ` Petteri Räty
2008-01-28 18:54 ` Ciaran McCreesh
2008-01-28 19:07 ` Petteri Räty
2008-01-28 20:43 ` Matthias B.
2008-01-28 23:52 ` Marius Mauch
2008-01-28 18:04 ` Robin H. Johnson
2008-01-30 17:35 ` Philip Webb
2008-01-30 18:32 ` Chris Gianelloni
2008-01-30 19:04 ` Chris Gianelloni
2008-01-30 18:33 ` Santiago M. Mola
2008-01-31 15:49 ` Natanael Copa
2008-01-31 23:46 ` Mike Frysinger
2008-02-01 12:18 ` Natanael Copa
2008-02-01 13:54 ` Mike Frysinger
2008-02-02 11:03 ` Natanael Copa
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=pan.2008.01.29.09.26.12@cox.net \
--to=1i5t5.duncan@cox.net \
--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