Mailinglist Archive: yast-devel (54 mails)

< Previous Next >
[yast-devel] libstorage plans?

Arvin mentioned in libstorage/pull/69 that there are "important and
fundamental changes required in libstorage". i'd like to know what
you (both Arvin and the team as a whole) plan in this regard?

after seeing some real-world problems with libstorage, and from my short
venture into its code i'd say the most pressing problem is the cylinder
as the base unit for partition positions and sizes, with the broken
class hierarchy (dynamic_cast...) distant second.

while these two may be the "worst", it does not necessarily make sense
to approach them first; it may be easier to postpone that until after
some other cleanup is done to make the code clearer. in this regard,
libstorage could use wider adoption of C++11 features like "auto" and
range-based loops.

so, what is your roadmap?

To unsubscribe, e-mail: yast-devel+unsubscribe@xxxxxxxxxxxx
To contact the owner, e-mail: yast-devel+owner@xxxxxxxxxxxx

< Previous Next >