ANNOUNCEMENT
============
This is the fourth preview of debimg, bringing support
for multiple disks (sets), a much improved dependency
resolver and more.
The next release will hopefully be debimg 0.1, if it can
satisfy the following requirements:
- Debian packages can be built (python-debimg and debimg)
- The configuration is not accessed directly by classes and
methods, the relevant keys are passed to them.
- The configuration format is frozen
ChangeLog: <http://alioth.debian.org/~jak-guest/ChangeLog-0.0.4>
Tarball: <http://alioth.debian.org/~jak-guest/debimg_0.0.4.tar.gz>
Website: <http://jak-linux.org/projects/debimg/>
commit 5a26e3061ca1af55aaa4278a13f5f76957df3517
Regards,
Julian Andres Klode
-- END OF ANNOUNCEMENT
QUESTIONS
=========
Bootloaders / install.ARCH directories
----------------------------------------
Details: The data for the bootloaders currently use the
directory /install. But on the final disc, e.g. install.386 is used.
This is somehow patched by debian-cd. Would it be possible to change the
location in the provided data instead. This makes development easier.
How to get the Kernel?
-----------------------
Details: Some architectures append the version to the kernel, others
not. Wouldn't it be possible to provide an index of these files?
=> main/installer-ARCH/current/images/ on the mirror
PowerPC for example, is hard to support at the moment, if you want to
support http and ftp sources.
Which architectures?
--------------------
Details: I would like to know which architectures are the most important
ones and therefore should be supported by debimg ASAP. (Currently only
i386 and amd64 are supported)
Do you like it?
---------------
Details: What do you like more? The configuration format of debimg or
the configuration format of debian-cd? Would you like debimg to support
the debian-cd format as well?
Have you already tried debimg?
-------------------------------
-- END OF QUESTIONS
0.1 STUFF
=========
Seperate configuration & core
---------------------------------
Currently, almost all classes in debimg somehow use the ConfigObj
instance or the DataList instance. This makes it impossible to quickly
change the configuration format or to create simple test scripts.
Therefore, all classes should work independent from the configuration.
Instead of getting values from the ConfigObj instances, the relevant
values are passed to the classes and their methods.
Provide a stable interface
----------------------------
debimg 0.1 will provide a stable API for developers. It allows them to
create their own applications, e.g. using debian-cd configuration files,
and to extend the current version of debimg. debimg 0.1 may also support
hooks, but this has not been decided yet.
Be ready
--------
debimg 0.1 needs to be ready for the users. Configuration has to be
easy, there should be support for migrating from debian-cd to debimg,
there should be documentation.
Roadmap
-------
Starting with October, there will be a release at the beginning of each
month.
2008-10 *Beta 1* Reorganize the code, seperate configuration & core
2008-11 *Beta 2* Add multi-arch functionality and other bootloaders
2008-12 *Candidate* Documentation added
2009-01 *Release* (New year)
Attachment:
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil