From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from pigeon.gentoo.org ([208.92.234.80] helo=lists.gentoo.org) by finch.gentoo.org with esmtp (Exim 4.77) (envelope-from ) id 1SpKTo-0000Vz-FR for garchives@archives.gentoo.org; Thu, 12 Jul 2012 14:34:56 +0000 Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id 6FA83E0517; Thu, 12 Jul 2012 14:34:48 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id D999CE02FB for ; Thu, 12 Jul 2012 14:34:14 +0000 (UTC) Received: from [192.168.1.145] (CPE002401f30b73-CM001cea3ddad8.cpe.net.cable.rogers.com [99.240.69.152]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: axs) by smtp.gentoo.org (Postfix) with ESMTPSA id 3EF981B4005 for ; Thu, 12 Jul 2012 14:34:14 +0000 (UTC) Message-ID: <4FFEE064.4000208@gentoo.org> Date: Thu, 12 Jul 2012 10:34:12 -0400 From: Ian Stakenvicius User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120625 Thunderbird/10.0.5 Precedence: bulk List-Post: List-Help: List-Unsubscribe: List-Subscribe: List-Id: Gentoo Linux mail X-BeenThere: gentoo-dev@lists.gentoo.org Reply-to: gentoo-dev@lists.gentoo.org MIME-Version: 1.0 To: gentoo-dev@lists.gentoo.org Subject: Re: [gentoo-dev] rfc: udev-rules.eclass References: <20120711191142.GA26844@linux1> <4FFDE8C6.40006@flameeyes.eu> <20120711234230.GA27226@linux1> <20120712091754.2480af4a@pomiocik.lan> <4FFED575.5090607@gentoo.org> <20120712161957.42264ad3@pomiocik.lan> In-Reply-To: <20120712161957.42264ad3@pomiocik.lan> X-Enigmail-Version: 1.3.5 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable X-Archives-Salt: 1cb3822a-3bc9-4e16-9569-d400ba9ee71c X-Archives-Hash: 38989f4e1369a0d72246b6e842bfba2c -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 12/07/12 10:19 AM, Micha=C5=82 G=C3=B3rny wrote: > On Thu, 12 Jul 2012 09:47:33 -0400 Ian Stakenvicius > wrote: >> Updating vdb shouldn't be an issue here, as long as pkg_postinst=20 >> doesn't crash mid-stream. Is the vdb common between package >> managers or does each one have a different solution? >=20 > Yes, it is common because for many years people keep noticing it > is common and using that. In other words, for many there is a > failing attempt to stop relying on its format. >=20 ..i'm not following this -- so it's common (ie, portage, paludis, etc all use it) because it's always been there? Anyways, if all the package managers do use it, then there isn't any reason at this juncture to not handle this via an update to vdb. If in the future different package managers use something different, then we'd need to have individual vdb-update scripts for each (differing) pms, but unless I misread you this is currently a non-issue.. -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iF4EAREIAAYFAk/+4GQACgkQ2ugaI38ACPDP8QD9HPv+l8vFW7cm/xA5ksKhUUyD xzOtVY93XLL3ArhqlYkBAJxi98IIk5qWib6BK7VckhQLwJVmmHO+xtDPFuhP78rU =3DYIIr -----END PGP SIGNATURE-----