[parted-devel] Introduction of a new parted-devel list member

[Albert ARIBAUD]

Harley D. Eades III wrote:

>>To synthesize the discussion with Harley: currently, ext2/3 is handled
>>by native code and indeed parted should switch to deferring some
>>ext2/3 "knowledge" to external code. Whether it should link to
>>libext2fs or call mke2fs/e2fsck/resize2fs (which use libext2fs
>>themselves) has yet to be decided, and the decision will also have to
>>take other filesystems into account.
> 
> I feel that only adding a single dependency is more realistic then to
> introduce many.  So IMHO linking to libext2fs would be more efficient.

OTOH, libext2fs is part of e2fsprogs, which contains e2fsck, resize2fs, 
mke2fs and the like, so the dependency does not really vary whether we 
consider using the lib or the progs.

In fact, I've seen changelog entries that mention changes in libext2fs 
likely to affect users of the lib but were hidden to users of the progs. 
Granted, this might be an isolated case; but still, I think we must look 
into it with no a priori opinion.

>>For the time being, I am setting up my devel environment and getting
>>familiar with the parted code. :)
> 
> Enjoy your journey..If you have any questions please feel free to
> ask. :)

I'm already asking questions, but so far these are directed to my Linux 
machine and take the general form of "why the heck do you need this old 
version of autoconf?" :)

Amicalement,
-- 
Albert.