From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from lists.gentoo.org (pigeon.gentoo.org [208.92.234.80]) by finch.gentoo.org (Postfix) with ESMTP id 8904813800E for ; Tue, 7 Aug 2012 07:53:00 +0000 (UTC) Received: from pigeon.gentoo.org (localhost [127.0.0.1]) by pigeon.gentoo.org (Postfix) with SMTP id A33E3E0678; Tue, 7 Aug 2012 07:52:46 +0000 (UTC) Received: from smtp.gentoo.org (smtp.gentoo.org [140.211.166.183]) by pigeon.gentoo.org (Postfix) with ESMTP id E1F7BE05F2 for ; Tue, 7 Aug 2012 07:52:10 +0000 (UTC) Received: from pomiocik.lan (77-254-77-13.adsl.inetia.pl [77.254.77.13]) (using TLSv1 with cipher DHE-RSA-AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: mgorny) by smtp.gentoo.org (Postfix) with ESMTPSA id 9A73A1B4036; Tue, 7 Aug 2012 07:52:09 +0000 (UTC) Date: Tue, 7 Aug 2012 09:52:48 +0200 From: =?UTF-8?B?TWljaGHFgiBHw7Nybnk=?= To: gentoo-dev@lists.gentoo.org Subject: [gentoo-dev] RFC: fsmove to profiles/updates Message-ID: <20120807095248.352544a3@pomiocik.lan> Organization: Gentoo X-Mailer: Claws Mail 3.8.1 (GTK+ 2.24.11; x86_64-pc-linux-gnu) 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 Content-Type: multipart/signed; micalg=PGP-SHA256; boundary="Sig_/7u56oKpeyyH6VyY5_XHZynt"; protocol="application/pgp-signature" X-Archives-Salt: ef5f0627-7ec7-4649-96a7-fdce3a7d256b X-Archives-Hash: c710a4a13138071543c63bf53e9a7cde --Sig_/7u56oKpeyyH6VyY5_XHZynt Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Hello, Right now, every time a bigger bunch of stuff (installed by various packages) needs to be moved around the filesystem, we have a lot of work to handle it somehow. And finally, users end up having to either rebuild a lot of packages to get the files in the new locations, or we do ugly things to move those files for them. I believe we should consider implementing something simpler. Thus, I propose introducing the following new command to profiles/updates: fsmove which -- at the moment of update -- will cause all PM-owned files in the old-location to be moved to the new one (recursively), updating the vdb as necessary. What remains to be solved/decided: 1. How to treat non-owned files? (leave them there, refuse to proceed with updates?) 2. How to handle relevant required updates? (packages which actually *have* to be updated before moving files) --=20 Best regards, Micha=C5=82 G=C3=B3rny --Sig_/7u56oKpeyyH6VyY5_XHZynt Content-Type: application/pgp-signature; name=signature.asc Content-Disposition: attachment; filename=signature.asc -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.19 (GNU/Linux) iJwEAQEIAAYFAlAgyVAACgkQfXuS5UK5QB2v8wP/cI7GabsYv/zn/2/Z++WBq0oF jsYvuZFgP2rJJh8aW2AP2GdMEbB7f9cKAm+rGN02rDWT3Tn8QPbvPQgwJZuQc1C1 bD/D+mARvBizYhfh4qrNAxH/Jhp5asmNM7nmyNxZM+fOqRBJxuGJBkkl8Q3n81mc LV0Wqf6PW+aWrvi9pbQ= =xMoH -----END PGP SIGNATURE----- --Sig_/7u56oKpeyyH6VyY5_XHZynt--