Am Tue, 7 Dec 2010 19:12:05 +0100 schrieb Tobias Powalowski :

This is a proper solution without making core a big monster again. greetings

Adding all filesystem tools to [core] won't make it a big monster. ;-) Heiko

Am Tue, 7 Dec 2010 23:25:06 -0500 schrieb Loui Chang :

I'm not so sure about that. There are probably more filesystems than I can imagine. I wouldn't be too thrilled if all of that was in core.

I only mean Linux filesystems which can be used for installing Linux, whether they are or can be used for /boot, /, or just /home, not such optional ones like vfat (dosfstools) or ntfs. Those vfat or ntfs partitions can easily be formatted and/or mounted after the installation. Their packages indeed belong into [extra]. I'm not sure if this list is complete, but these are the ones which come to my mind: ext2 ext3 ext4 reiserfs reiser4 btrfs nilfs jfs xfs nfs So those packages are affected: e2fsprogs reiserfsprogs btrfs-progs(-unstable) nilfs-utils jfsutils xfsprogs nfs-utils Most of these packages are already in [core] anyway. And those tools are not the biggest ones. So [core] won't become a monster if they would be moved into it. But all of them should be removed from (base). Heiko

On Wed, Dec 08, 2010 at 11:18:20AM -0200, Armando M. Baratti wrote:

Em 08-12-2010 09:57, Heiko Baums escreveu:

...

Am Tue, 7 Dec 2010 23:25:06 -0500 schrieb Loui Chang:

So those packages are affected: e2fsprogs reiserfsprogs btrfs-progs(-unstable) nilfs-utils jfsutils xfsprogs nfs-utils

package files =============== ===== e2fsprogs already in core reiserfsprogs already in core btrfs-progs(-unstable) 124 KB 1 MB nilfs-utils 79 KB 336 KB jfsutils already in core xfsprogs already in core nfs-utils already in core

Armando

I highly doubt that this was _ever_ a question of size in the repos. More likely, It's a matter of time vs. gain for a small number of volunteers. If you're a user who knows that they want a particular exotic filesystem that isn't widely used, you the user, on this very day, have the following exciting options including but not limited to: 1) dont use AIF. not to sleight Dieter, but there's more ways to install Arch than just by using AIF. 2) format and mount the partitions yourself, convince AIF that this has been done, and continue installing as you like, with AIF. I've done this before with btrfs, as have others. 3) use Archboot, which supports a wider range of packages. Being the capable and intelligent user who clearly has sufficient reason for wanting such a thing, I'm sure you can think of other ways to accomplish your goal. d

Am Wed, 8 Dec 2010 08:56:24 -0500 schrieb Dave Reisner :

I highly doubt that this was _ever_ a question of size in the repos. More likely, It's a matter of time vs. gain for a small number of volunteers. If you're a user who knows that they want a particular exotic filesystem that isn't widely used, you the user, on this very day, have the following exciting options including but not limited to:

That may be true for packages in [extra], but not for [core]. [core] is meant for providing and being able to install a minimal base system. And a filesystem, regardless of which, is one of the most basic and necessary packages. And AIF is the official installer. It's meant for installing this base system. So, no, in this case you're wrong. As I said before, then you could just provide ext4, because you resp. the devs think that's the one and only filesystem, and everyone who needs a different filesystem for whatever reason, has to make an LFS out of Arch Linux. Well, I know it's a bit exaggerated. Heiko

Am Mittwoch 08 Dezember 2010 schrieb Heiko Baums:

Am Wed, 8 Dec 2010 08:56:24 -0500

schrieb Dave Reisner :

...

3) use Archboot, which supports a wider range of packages.

But Archboot has some other disadvantages. It's not as flexible as Archiso and doesn't give me as many options as Archiso, e.g. I can't change or control the cryptsetup options and I don't know with which options the LUKS container are created. And it has far too many packages in it's software selection.

Heiko Well about cryptsetup, i don't think AIF let you control much more things, you can also use any encryption you want if you use commandline, else tell me what is not working, it shouldn't be hard to implement in archboot.

greetings tpowa -- Tobias Powalowski Archlinux Developer & Package Maintainer (tpowa) http://www.archlinux.org tpowa@archlinux.org

At Mittwoch, 8. Dezember 2010 05:45 Loui Chang wrote:

Ask Microsoft to support every filesystem in existence on their standard install CD and core system and maybe us poor Archers with our limited time and budget can also rise to your stratospheric expectations.

Bad example because MS offers only two filesystem and a better example of a bad installer from a big company is the one from redhat (+ the forks of it) because with this you can't format all filesystems (and more worse it is that the default kernel don't support this filesystems too). The archlinux installer do in this case a very good job from my memory. At the time of installing archlinux i have had the choice of all what i want and to have the *utils from the filesystem on the cd too would be very nice. And just my 2c about the example of btrfs: Without a fsck i would never take a look at it instead of the very good reports about it be very attractice. See you, Attila