> It then will break all #include of headers since we'll need to change > from > > #include <parted/parted.h> > > to > > #include <parted2.0/parted.h> > > and others too, of course.
Ah yes, I see the practical difficulties now. So I guess the best way to go about this is to include comprehensive information about how Parted 2.0 will differ from earlier versions. Since we are also planning for an API change; this might not hurt developers much. -- Anant _______________________________________________ parted-devel mailing list [email protected] http://lists.alioth.debian.org/mailman/listinfo/parted-devel
