Received: from spf3.us4.outblaze.com (spf3.us4.outblaze.com [205.158.62.25]) by sdf.lonestar.org (8.12.10/8.12.10) with ESMTP id iALJQ44h028562 for ; Sun, 21 Nov 2004 19:26:04 GMT Received: from lists.gnu.org (lists.gnu.org [199.232.76.165]) by spf3.us4.outblaze.com (Postfix) with ESMTP id 226C254322 for ; Sun, 21 Nov 2004 19:26:05 +0000 (GMT) Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CVxUa-0003fg-2T for migo@homemail.com; Sun, 21 Nov 2004 14:35:24 -0500 Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.33) id 1CVxTz-0003fN-0F for gnu-arch-users@gnu.org; Sun, 21 Nov 2004 14:34:47 -0500 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.33) id 1CVxTy-0003eM-4N for gnu-arch-users@gnu.org; Sun, 21 Nov 2004 14:34:46 -0500 Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.33) id 1CVxTw-0003e7-QW for gnu-arch-users@gnu.org; Sun, 21 Nov 2004 14:34:46 -0500 Received: from [212.71.168.94] (helo=vagabond.light.src) by monty-python.gnu.org with esmtp (Exim 4.34) id 1CVxKt-0001Mu-M2 for gnu-arch-users@gnu.org; Sun, 21 Nov 2004 14:25:24 -0500 Received: from bulb by vagabond.light.src with local (Exim 3.36 #1 (Debian)) id 1CVxKm-0001vV-00; Sun, 21 Nov 2004 20:25:16 +0100 Date: Sun, 21 Nov 2004 20:25:16 +0100 From: Jan Hudec To: Nathan Howell Subject: Re: [Gnu-arch-users] Excluded files should actually be excluded Message-ID: <20041121192516.GF2870@vagabond> References: <1100989864.32754.31.camel@localhost.localdomain> Mime-Version: 1.0 In-Reply-To: <1100989864.32754.31.camel@localhost.localdomain> User-Agent: Mutt/1.5.6+20040907i Cc: gnu-arch-users@gnu.org X-BeenThere: gnu-arch-users@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: a discussion list for all things arch-ish List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: multipart/mixed; boundary="===============0204050261==" Sender: gnu-arch-users-bounces+migo=homemail.com@gnu.org Errors-To: gnu-arch-users-bounces+migo=homemail.com@gnu.org Status: RO Content-Length: 3602 Lines: 94 --===============0204050261== Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="O9uFcEIpmYvy18ul" Content-Disposition: inline --O9uFcEIpmYvy18ul Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable On Sat, Nov 20, 2004 at 14:31:04 -0800, Nathan Howell wrote: > I've been working on getting my home dir into arch recently, and have > run into a couple of snags. Here's the setup. I've tried doing this > before, using configs and several separate projects for different sets > of config files. I found it too cumbersome to maintain, so I'm now using > one big project in ~, with certain directories (mostly large ones) > excluded either because I never want them in an archive or because they > will be their own projects.=20 >=20 > The main project is set to tagline, with untagged-source source set. > This is basically to keep my options open, and to make it easy to > maintain. I don't want to spend a ton of time dealing with adding and > removing files, so I'm essentially using names, but I want the option of > using taglines and explicit ids when I wish to (since I already have > taglines in most of the config files that I care about).=20 >=20 > Here are the problems/questions: >=20 > 1. When I specify files to exclude (in .arch-inventory), they aren't > actually ignored by arch at all times. They are still considered (all > the excluded dirs are still traversed), and this slows everything down. > At this point, it is also preventing me from committing my files. A > couple of excluded directories have files with unicode chars in them, > things like accented e's and such, which apparently violate naming > conventions. Since I don't even want these files in the archive in the > first place, having them stop my commit completely is quite frustrating. > I need to make arch completely ignore these files. Possible? The "excluded" files mean they are excluded from listing, NOT revision control. Use precious if you don't want them under revision control. > 2. I can see wanting to commit files with accented unicode chars in the > names in the future. Is this going to be possible at some point? Some > point soon? Until Tom makes his mind about what is the right way to handle unicode, you are out of luck. > It seems odd to me that excluded files aren't excluded. Is there a > reason behind this, or is it a bug? Besides preventing my commit at the > moment, this currently makes the output of tla useless, since it lists > every excluded file as "apparent source, but lacks an id". There are > many thousands of them. I really don't need that list. It is a misleading name. ---------------------------------------------------------------------------= ---- Jan 'Bulb' Hudec --O9uFcEIpmYvy18ul Content-Type: application/pgp-signature; name="signature.asc" Content-Description: Digital signature Content-Disposition: inline -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.2.5 (GNU/Linux) iD8DBQFBoOucRel1vVwhjGURAhB6AKDYgP1yY7P8C0b/N2m+2dMNwVUArACgxx/5 WztT9aDd2aa/vSqZn76hYfU= =9AVZ -----END PGP SIGNATURE----- --O9uFcEIpmYvy18ul-- --===============0204050261== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline _______________________________________________ Gnu-arch-users mailing list Gnu-arch-users@gnu.org http://lists.gnu.org/mailman/listinfo/gnu-arch-users GNU arch home page: http://savannah.gnu.org/projects/gnu-arch/ --===============0204050261==--