From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from lists.gentoo.org ([140.105.134.102] helo=robin.gentoo.org) by nuthatch.gentoo.org with esmtp (Exim 4.43) id 1Dy8w0-0002Bj-0q for garchives@archives.gentoo.org; Thu, 28 Jul 2005 14:00:28 +0000 Received: from robin.gentoo.org (localhost [127.0.0.1]) by robin.gentoo.org (8.13.4/8.13.4) with SMTP id j6SDxLdS026621; Thu, 28 Jul 2005 13:59:21 GMT Received: from smtp.gentoo.org (smtp.gentoo.org [134.68.220.30]) by robin.gentoo.org (8.13.4/8.13.4) with ESMTP id j6SDvhE6005307 for ; Thu, 28 Jul 2005 13:57:43 GMT Received: from p061198140228.ppp.prin.ne.jp ([61.198.140.228] helo=opteron246.suzuki-stubbs.home) by smtp.gentoo.org with esmtpa (Exim 4.43) id 1Dy8tl-0006bF-8x for gentoo-dev@lists.gentoo.org; Thu, 28 Jul 2005 13:58:11 +0000 Received: by opteron246.suzuki-stubbs.home (Postfix, from userid 1000) id 17916100E42; Thu, 28 Jul 2005 22:58:42 +0900 (JST) From: Jason Stubbs To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] Changelogs Date: Thu, 28 Jul 2005 22:58:39 +0900 User-Agent: KMail/1.8.1 References: <42E6EBFD.5000003@egr.msu.edu> <200507272350.24502.jstubbs@gentoo.org> <42E8209A.2000702@egr.msu.edu> In-Reply-To: <42E8209A.2000702@egr.msu.edu> Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 Content-Type: multipart/signed; boundary="nextPart1759576.8W4eCN6A0T"; protocol="application/pgp-signature"; micalg=pgp-sha1 Content-Transfer-Encoding: 7bit Message-Id: <200507282258.41763.jstubbs@gentoo.org> X-Archives-Salt: 08594a79-8313-45d8-b425-dced1c9abced X-Archives-Hash: 3f3c58faa3c2231e9342b2e34c2422bc --nextPart1759576.8W4eCN6A0T Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable Content-Disposition: inline On Thursday 28 July 2005 09:02, Alec Warner wrote: > In hindsight, arguing over almost two different things. We both agree > that upgrade paths for changes that break the system are good, and that > information regarding the upgrade path *SHOULD* be provided in some > manner. Some developers think that providing detailed instructions in > pkg_postinst() is good, others will direct you to a website ( usually > UPSTREAM's webpage ) which has the instructions; it saves them time. > Which is correct, or are both? Both are correct. Some developers are willing to put the effort into getting upgrade info immediately before the user and some are happy with the user putting 50% of the effort. Either is fine, but you're also missing major changes that happen in ebuilds themselves. The real point, though, is that there should be a consistent way for this information to be delivered to users. Whether is be via ChangeLog, metadata.xml or pkg_warn(), the requirement is that developers are able to provide as little or much information as they want in such a way that users get easy access to it. > In the former case where more specific information is provided to the > user by portage you generally want a more complex system. You want the >=20 > "You enabled baduse? > Removing it will rm -rf /!" syntax ( from our conversation last > night ) which is decidedly more complex to write and more complex to pars= e, >=20 > Don't get me wrong, I like it, but I doubt it will get used by enough > people to be useful. I never said I wanted that. I just used it to illustrate how it could be easily handled in metadata.xml rather than pkg_warn() if necessary. Nor is it complex to write or parse. My heart is not set on the above in any way whatsoever, though. I think you might be jumping to a solution without fully considering the problem. On the whole, this is a relatively small problem anyway, so an immediate solution is not really necessary. =2D-=20 Jason Stubbs --nextPart1759576.8W4eCN6A0T Content-Type: application/pgp-signature -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQBC6OSRxvWNPsk/ZP4RAgshAKChWqAew/JzC3v0O/kC7uD0DuGqewCgsIoP ZQDdQmsvnXTZF4ROiFmc3Gs= =vztB -----END PGP SIGNATURE----- --nextPart1759576.8W4eCN6A0T-- -- gentoo-dev@gentoo.org mailing list