From: "Claes Ström" <gentoodevlist@clabbe.com>
To: <gentoo-dev@gentoo.org>
Subject: [gentoo-dev] Some thougts about portage/emerge/ebuilds...
Date: Thu, 29 May 2003 23:23:31 +0200 [thread overview]
Message-ID: <007801c32628$8de665e0$3a0a640a@DOMLINA> (raw)
Hi devs!
Here is some thoughts I have about portage/emerge/ebuilds
1.
manpage don't tell me that -D = --deep (need to read pythonsource or read
response from "emerge --help" to figure out )
2.
When new things coming up like "fixpackages" and emerge responds that you
should change "FEATURES" or run "fixpackages". When this script is outside
of normal path, it would be nice if it was some hint where it's located.
(/usr/lib/portage/bin/fixpackages)
3.
When you do a deep pretended update world (emerge -vpuD world) and finds
some updates like: [ebuild U ] dev-libs/glib-2.2.1-r1 [2.2.1] -doc
Then when you read Changes for this package and get a diff like this of the
ebuilds:
--- glib-2.2.1.ebuild 2003-03-30 23:27:33.000000000 +0200
+++ glib-2.2.1-r1.ebuild 2003-05-29 09:39:53.000000000 +0200
@@ -1,6 +1,6 @@
# Copyright 1999-2003 Gentoo Technologies, Inc.
# Distributed under the terms of the GNU General Public License v2
-# $Header: /home/cvsroot/gentoo-x86/dev-libs/glib/glib-2.2.1.ebuild,v 1.9
2003/03/30 21:27:33 joker Exp $
+# $Header: /home/cvsroot/gentoo-x86/dev-libs/glib/glib-2.2.1-r1.ebuild,v
1.1 2003/05/29 07:39:53 utx Exp $
inherit libtool
@@ -42,6 +42,18 @@
src_install() {
einstall || die
+
+ # Consider invalid UTF-8 filenames as locale-specific.
+ dodir /etc/env.d
+ echo "G_BROKEN_FILENAMES=1" >${D}/etc/env.d/50glib2
dodoc AUTHORS ChangeLog COPYING README* INSTALL NEWS NEWS.pre-1-3
}
+
+pkg_postinst() {
+ env-update
+}
+
+pkg_postrm() {
+ env-update
+}
Why should I need to rebuild the whole glib2 to get one line appended to
/etc/env.d/50glib2 ?
Wouldn't it be nice if portage could handle small file updates instead of
rebuilding from scratch!
4.
I've seen many "etc-updates" with only "cvs-header-updates"!
It would be *nice* if "ebuild-devs" check this before releases...
BTW it looks like forums.gentoo.org is down!
My 2 USE-flags
Claes Ström
PS
I'm also think that the homepage should have more news/information collected
from the Forum, IRC, Bugzilla and mailing-lists. It could be done by some
"junior wannabes" who have time to "hang out" around the clock and trawl all
sources mentioned above and do some editorial work (daily).
Things like framebuffer- and icon-"toys" should have an own track
(for all the newbies who loves that stuff).
--
gentoo-dev@gentoo.org mailing list
next reply other threads:[~2003-05-29 21:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-05-29 21:23 Claes Ström [this message]
2003-05-30 8:59 ` [gentoo-dev] Some thougts about portage/emerge/ebuilds Michael Kohl
2003-05-30 12:27 ` Daniel Armyr
2003-05-30 17:36 ` wes chow
-- strict thread matches above, loose matches on Subject: below --
2003-05-29 22:37 Adam Mercer
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='007801c32628$8de665e0$3a0a640a@DOMLINA' \
--to=gentoodevlist@clabbe.com \
--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