From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 30422 invoked by uid 1002); 29 Apr 2003 03:32:40 -0000 Mailing-List: contact gentoo-dev-help@gentoo.org; run by ezmlm Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Received: (qmail 13721 invoked from network); 29 Apr 2003 03:32:39 -0000 Date: Mon, 28 Apr 2003 23:32:39 -0400 From: Aron Griffis To: gentoo-dev@gentoo.org Message-ID: <20030429033239.GB413@time> Mail-Followup-To: gentoo-dev@gentoo.org References: <20030429001443.GA413@time> <20030429011644.GB18711@lucien.dreaming> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20030429011644.GB18711@lucien.dreaming> User-Agent: Mutt/1.5.4i Content-Transfer-Encoding: quoted-printable Subject: Re: [gentoo-dev] Re: new local USE var: vim-with-x X-Archives-Salt: 65f1703c-bfe8-4580-b7e7-b7612fb8b31f X-Archives-Hash: f7ac952d9b99a3a8c424a6e874c9c754 Hi Bj=F6rn, Bj=F6rn Lindstr=F6m wrote: [Mon Apr 28 2003, 09:16:44PM EDT] > This is really ugly. The expected behaviour would doubtlessly be that > USE=3DX means that vim will have X support. >=20 > Wouldn't using X combined with a suitable ewarning be better? Unfortunately I think you are wrong. Most users that I have encountered do not expect "emerge vim" to pull in xfree, even when USE=3DX. This is = a very frequently asked question on IRC and in the mailing lists. Here is the history of the behavior in the vim ebuild: 1. The original vim ebuilds had "X? ( x11-base/xfree )". This confused a lot of users who did not expect their first action of "emerge vim" to also demand xfree. Adding warnings is not really sufficient since the damage has been done when they hit enter; portage will start with the first dependency in the list, not with the vim ebuild itself. 2. The next solution was to leave xfree out of DEPEND. In this case, USE=3DX was honored, but only if xfree was already merged on the system. This is clearly wrong since it has a dependency on the environment which is not controlled by the ebuild. As a resuilt, some users would have one thing and other users would have another. 3. Next, I changed vim to refrain from linking against X altogether, on the assumption that the gvim ebuild would bu sufficient for users wanting an X-linked ebuild. 4. Finally, I made the behavior dependent on a local USE var, trying to capture the expectations of the typical user, while providing an escape route for those particular users who want a vim linked against the X libraries. Keep in mind this is not a gui version of vim (that is provided by the gvim ebuild), it's just the particular bits that allow X interaction while in a terminal. For example, xterm title setting, X clipboard support for vim selections, and moving the cursor using the mouse. I have seen very few users that demand those particular features from vim, so it doesn't make sense to me to give the vim ebuild such a heavy dependency. > ...or perhaps ignoring USE=3DX and use USE=3Dgtk(2?) and possibly USE=3D= kde > instead? I find it hard to believe that would be an improvement. The vim ebuild clearly doesn't depend on those toolkits; they're used by the gvim ebuild. No user is going to have a clue that USE=3Dkde is causing their console vim ebuild to pull in xfree... Thanks for your suggestions. If you can convince me there's a better way than what I've done, I'll gladly consider making the change in the ebuild. :-) Aron -- gentoo-dev@gentoo.org mailing list