Hi Ralf & Bimal,<br><br>The deadline is quickly approaching, but since I have worked with RTEMS<br>on Debian Systems quite a bit I'll throw in my two cents ...... <br>Since Ralfs questions quite come to the point I'll just reply to them.<br>
<br><div class="gmail_quote">
On Sun, Mar 30, 2008 at 9:29 AM, Ralf Corsepius <<a href="mailto:ralf.corsepius@rtems.org" target="_blank">ralf.corsepius@rtems.org</a>> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Hi Bimal,<br>
<br>
I think, I am the one to answer this - Please bare with me if I might be<br>
missing some information, but I have been AFK most of the time last week<br>
and have my rtems mail folder filled with dozens of unread mails ;)<br>
<br>
<br>
First of all, thanks for wanting to take a stab on this.<br>
<br>
So, let me ask a couple of questions wrt. proposal:<br>
<br>
1. What do you want to package?<br>
The GNU-toolchains (binutils, newlib, gcc, gdb) or RTEMS itself?</blockquote><div>RTEMS itself is the least usefull of them. In my opinion it only makes sense,<br>to quickly run the demo applications in a simulator. Altough you could<br>
also create a RTEMS Source Package.<br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<br>
2. Which distributions do you want to address?<br>
Like with rpm-based distros, there exists a plethora of Debian'ish<br>
packaged distros, not only one.</blockquote><div>I have built the RTEMS toolchain with pbuilder. With pbuilder it is<br>very, very easy to build for various different debian'ish systems.<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
3. Though I agree that deb packages would be convenient users of<br>
Debian'ishly packaged distros, I question the technical need to do so,<br>
because at least on original Debian distros it had been possible to use<br>
"alien" to import rpms. Doesn't this apply anymore?</blockquote><div>Altough the idea of alien is brilliant, in my experience it rarely works without hassle.<br>I have ended up building .deb for rtems-bfin because I was too stupid to install<br>
your (Ralfs) rpms with alien on my ubuntu system. <br><br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
<div><div></div><div><br>
<br>
On Sun, 2008-03-30 at 15:31 +0530, bimal varghese wrote:<br>
> i am attaching my<br>
> proposal for creating a debian package for RTEMS<br>
> any suggestions for improvement and correction of errors<br>
> in the proposals are accepted<br>
<br>
</div></div>Comments interspersed:<br>
<br>
> Title<br>
> -----<br>
><br>
> Creating Debian package for RTEMS<br>
><br>
><br>
> Synopsis<br>
> --------<br>
><br>
> I will build a debian package for RTEMS with all dependencies<br>
> taken<br>
> care of. I will also write shell/Perl scripts which makes it possible<br>
> to<br>
> automate the package creation process. </blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
Our build-machines all are Fedora-i386 and Fedora-x86_64-based.<br>
<br>
Do you plan to add cross-distribution packaging (e.g. building Debian<br>
packages on Fedora or Debian/i386 on Ubuntu/x86_64)?</blockquote><div>As mentioned before, Debian -> Ubuntu is quite easy but building<br>everything on a Fedora machine might be a bit more challenging. <br></div>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
> Project Schedule<br>
> ----------------<br></blockquote><div>..... <br></div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;"><br>
> July 28,2008: The complete integreted Debian package is generated and<br>
> tested on various systems.<br>
More details, please. What and which do you have in mind?<br>
</blockquote><div><br>I would plan a more iterative approach. Start with one target architecture test,<br>generate for the next target architecture. I would also suggest to create not<br>one huge package but more smaller packages. Another very important point<br>
is to reuse Ralfs patches for the GCC/RTEMS toolchain. He has put and still puts <br>>>alot<< of work into them and it should absolutely be avoided that this work has<br>to be duplicated. <br><br><br>just my two cents .....<br>
<br>alain<br></div></div><br>