From mboxrd@z Thu Jan 1 00:00:00 1970
Return-Path: <gentoo-portage-dev+bounces-5740-garchives=archives.gentoo.org@lists.gentoo.org>
Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80])
by finch.gentoo.org (Postfix) with ESMTP id D3D68138262
for <garchives@archives.gentoo.org>; Fri, 20 May 2016 04:14:27 +0000 (UTC)
Received: from pigeon.gentoo.org (localhost [127.0.0.1])
by pigeon.gentoo.org (Postfix) with SMTP id ED035E0804;
Fri, 20 May 2016 04:14:24 +0000 (UTC)
Received: from plane.gmane.org (plane.gmane.org [80.91.229.3])
(using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits))
(No client certificate requested)
by pigeon.gentoo.org (Postfix) with ESMTPS id 52CBDE0801
for <gentoo-portage-dev@lists.gentoo.org>; Fri, 20 May 2016 04:14:24 +0000 (UTC)
Received: from list by plane.gmane.org with local (Exim 4.69)
(envelope-from <glgpd-gentoo-portage-dev@m.gmane.org>)
id 1b3bpN-0002tE-Dc
for gentoo-portage-dev@lists.gentoo.org; Fri, 20 May 2016 06:14:21 +0200
Received: from ip98-167-165-199.ph.ph.cox.net ([98.167.165.199])
by main.gmane.org with esmtp (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <gentoo-portage-dev@lists.gentoo.org>; Fri, 20 May 2016 06:14:21 +0200
Received: from 1i5t5.duncan by ip98-167-165-199.ph.ph.cox.net with local (Gmexim 0.1 (Debian))
id 1AlnuQ-0007hv-00
for <gentoo-portage-dev@lists.gentoo.org>; Fri, 20 May 2016 06:14:21 +0200
X-Injected-Via-Gmane: http://gmane.org/
To: gentoo-portage-dev@lists.gentoo.org
From: Duncan <1i5t5.duncan@cox.net>
Subject: [gentoo-portage-dev] Re: [PATCH] repoman: declare '-x', '--xmlparse' command line
options obsolete
Date: Fri, 20 May 2016 04:14:13 +0000 (UTC)
Message-ID: <pan$c3533$a4c1a334$5da8cba6$bfcb3c4@cox.net>
References: <1463697929-10480-1-git-send-email-gokturk@gentoo.org>
Precedence: bulk
List-Post: <mailto:gentoo-portage-dev@lists.gentoo.org>
List-Help: <mailto:gentoo-portage-dev+help@lists.gentoo.org>
List-Unsubscribe: <mailto:gentoo-portage-dev+unsubscribe@lists.gentoo.org>
List-Subscribe: <mailto:gentoo-portage-dev+subscribe@lists.gentoo.org>
List-Id: Gentoo Linux mail <gentoo-portage-dev.gentoo.org>
X-BeenThere: gentoo-portage-dev@lists.gentoo.org
Reply-to: gentoo-portage-dev@lists.gentoo.org
Mime-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
X-Complaints-To: usenet@ger.gmane.org
X-Gmane-NNTP-Posting-Host: ip98-167-165-199.ph.ph.cox.net
User-Agent: Pan/0.141 (Tarzan's Death; GIT fefda68dd)
X-Archives-Salt: 727b38b6-0074-4b65-a10f-72317e3cf015
X-Archives-Hash: 2dbb575799ede7701c02d87334f6bf5a
Göktürk Yüksek posted on Thu, 19 May 2016 18:45:29 -0400 as excerpted:
> Repoman pulls in lxml unconditionally now and performs metadata checks
> by default. This behavior makes these command line options obsolete
> since forcing the default makes little sense. Declare them obsolete
> instead of removing them for backwards compatibility.
I like the general idea, but not the implementation. =:^(
Example...
> -\fB-x\fR, \fB--xmlparse\fR
> -Forces the metadata.xml parse check to be carried out
> +\fB-x\fR, \fB--xmlparse\fR (OBSOLETE)
Often I'll find some online resource that recommends some command, but I
(arguably wisely!) prefer to check the manpage to see what a command and
its recommended options actually do, as opposed to just running it. That
way, in addition to protecting myself from rm -rf .* type advice as
sometimes found online, I learn as I go and can then apply the new
knowledge to similar situations, instead of being lost when an arbitrary
command copied without understanding doesn't work.
Or maybe I'm simply trying to fix an old, poorly documented script that
just broke, and am trying to figure out what some command therein
actually does.
The problem is outdated options with no hint as to what they actually did
before they were obsoleted and how to proceed with updating them for use
with newer versions. Were they obsoleted by more flexible options so the
old version isn't needed but I need to figure out what new option to use
and its format? Is that behavior now the default? Was that
functionality removed and thus is no longer available?
So please, don't just declare it obsolete without saying what it actually
did and if it applies, what the current equivalent might be. Doing so is
if anything even more frustrating to someone trying to figure out what
the option actually did, than removing it from the documentation entirely!
So, perhaps (I'm not going to attempt formatting)...
--xmlparse (Obsolete, formerly forced a metadata.xml parse check but
that's now default behavior.)
That way, anyone seeing the option somewhere in old code will still be
able to lookup what it did, and know that they can simply mentally ignore
that option when mentally tracing the old code in their head and delete
it in their updated version, because it's now the default.
--
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