David Cantrell <[EMAIL PROTECTED]> writes:
> Just to be clear... I'd prefer this parted-ng directory to be inside
> the master branch checkout. Not another branch. So you'd check out
> the master branch code and see these directories inside the project:
>
> parted/
> parted-ng/
> libparted/
>
> While we are releasing 1.9.x, users will get both the current
> parted(8) user interface *and* the parted-ng(8) user interface. Once
> we deem parted-ng good, we remove parted and rename parted-ng to
> parted.
>
> That was my idea.
Ack.
>> My personal idea about the design of it would be:
>>
>> - modular;
>>
>> - plugin based;
>>
>> - completely new code;
>>
>> Doing it, we'll discover which parts of code will be used a lot and
>> then those would be merge on the library itself. Without this I think
>> will be difficult to identify the right parts of code that should be
>> merge and which shouldn't.
>>
>> Please, comment on it.
>
> I would like it to support sfdisk(8) scripts. The plugin idea is
> really good.
The sfdisk mode could be another plugin (or module).
--
O T A V I O S A L V A D O R
---------------------------------------------
E-mail: [EMAIL PROTECTED] UIN: 5906116
GNU/Linux User: 239058 GPG ID: 49A5F855
Home Page: http://otavio.ossystems.com.br
---------------------------------------------
"Microsoft sells you Windows ... Linux gives
you the whole house."
_______________________________________________
parted-devel mailing list
[email protected]
http://lists.alioth.debian.org/mailman/listinfo/parted-devel
