Gentoo Archives: gentoo-dev

From: Dan Armak <danarmak@g.o>
To: gentoo-dev@××××××××××.org
Subject: Re: [gentoo-dev] additional files in portage tree
Date: Wed, 08 Aug 2001 11:58:22
Message-Id: 01080820574407.00611@localhost
In Reply to: Re: [gentoo-dev] additional files in portage tree by Parag Mehta
1 On Wednesday 08 August 2001 20:25, you wrote:
2 > Hi Ben!
3 >
4 > * Ben Lutgens assembled some ascibets to say:
5 > Ben >Hi all, I am proposing we add a new file to the portage tree
6 > directories. I Ben >was thinking something like the pkg_descr files in
7 > freebsd ports. It could Ben >have a slightly more detailed description, the
8 > install process ( from the Ben >portage point of view ) as well as homepage
9 > and ftp urls and possibly a Ben >brief gentoo-changelog. It could look
10 > something like this.
11 > Ben >I just think it'd be nice to have a file that we can less to find out
12 > what Ben >a package is, sometimes the name isn't enough as I can't possibly
13 > keep Ben >straight everything and the DESCRIPTION in the ebuild isn't great
14 > since Ben >noone wants to clutter everything up.
15 > Ben >
16 > Ben >I'm also not suggesting we take the next 3 months to write these for
17 > the Ben >existing packages, just adding them for new ones or possibly when
18 > updating.
19 >
20 > I'm all for it.
21 >
22 > also it would be nice if it could be interactive in way that when :
23 >
24 > emerge foo.ebuild
25 > it shows the pkg_descr()
26 > thenruns the emerge --pretend foo.ebuild
27 > and then asks the user whether to go ahead or not ?
28 >
29 > and the user can bypass the interactivity by passing one more parameter as
30 > : emerge --nopretend foo.ebuild
31 What you want is reverse the default value of pretend emerges (i.e. pretend
32 by default) and of interactiveness (which is currently non-existent, but by
33 your system a user would have to confirm building after running emerge).
34 IMHO, and as a personal opinion, I like things better the way they are now.
35 But if it comes to that I suppose this can be made configurable easily enough.
36
37 As for the description files: I think there'll always be large blanks and
38 ebuilds without descriptions. The important thing will be to remember that
39 there were no descriptions and now there are some. New users might fall to
40 thinking there are "supposed" to be descriptions but usually aren't, and
41 psychologically that's a worse impression than no descriptions at all. I
42 don't know how true-to-life I'm picturing the users here :-)
43 Except for that it obviously can only help, so let's go ahead with it!
44
45
46 --
47
48 Dan Armak
49 Gentoo Linux Developer, Desktop Team
50 Matan, Israel