Re: emdebian project status
Philippe De Swert wrote:
> Hello all,
>
> On Thu, 2005-07-21 at 15:47 +0200, Fathi BOUDRA wrote:
>
>>>this is a major problem. There is no HowTo because the project is in an
>>>early stage ... it under heavy development and I guess people like
>>>rather to code than to write HowTos ;-)
>
>
> Indeed we are trying to get something together
>
>
>>it's not really active because it lacks of documentation. there isn't an easy
>>way to try and test emdebian, not really user oriented.
>
>
> The people working on this have been vastly overloaded with work on
> other things which has been causing a more or less freeze on their
> ability to work on this. Debconf has enabled us to have some discussions
> about how to proceed and we are making plans now to be able to get this
> going again. Hopefully we will be able to fix all the shortcomings (big
> task) to make this a workable and usable project.
I spoke with Wookey on the Debconf5. It seems the major problem is that
the developers (which could contribute) do not know in which direction
we are going. So they can not really contribute.
We lack a bird's eye view to point people in the right direction.
It would help massively if someone of the active people (the ones who
know how the system is supposed to work) could make a short summary
where we are going at the moment.
The questions I have is:
* how do we create a simple, minimalistic FS (in a Debian way)?
* minimalistic base system? (remove of package dependencies which are
not needed on an embedded device)
* is emdebian integrated into the main archive?
* if yes, how is emdebian integrated into the source packages system?
* what about binary packages and repositories?
* do we need a special EmDebian Guideline, because a lot of files which
have to be in a Debian package are completely pointless on an embedded
system (changelogs, copyright texts etc.)?
With all the documentation I have I was not able to figure out:
* what role the stag framework is playing
* is now cross compiling handled with the normal dpkg-cross, an
unofficial dpkg-cross, stag itself?
* how do we cross compile in a debian way?
What is my vision of Emdebian:
a) select architecture (CPU)
b) based on selection in a) a tool provides me a source package
repository from which I can choose:
* base system (pre selected)
* desired packages (the number of packages would heavily depend on
selection a)
c) make source package selection
d) create binary archive from this selection in c) which is stored as an
archive on my machine (I assume making a binary archive for each of the
architectures is not feasible) - this will take a long time when it is
created the 1st time
e) choose a selection from the set of binary packages in the local
binary repository
f) create root-FS like like debootstrap using the packages selected in e
g) get kernel, tweak kernel parameters, kompile kernel, install kernel
h) tweak system parameters (like mount points etc.)
i) test system using a virtual machine (or the real hardware)
regards Max
--
Max Hofer
APUS Software G.m.b.H.
A-8074 Raaba, Bahnhofstraße 1/1
T| +43 316 401629 11
F| +43 316 401629 9
W| www.apus.co.at
E| max.hofer@apus.co.at
Reply to: