Hi, Jiri. 2013/12/17 Jiri Svoboda <[email protected]>
> Hi Vojta, > > I really aplaud your achievements and I am looking forward to trying it > out :-D. On the other hand I really don't understand your separatist > tendencies. Why use a separate private issue tracker on GitHub and a > separate private repo on GitHub? IMO coastline should be either merged to > mainline. Even in the case we actually decided to keep it in a separate > repo (why?) then why not host it on the official server along mainline. And > why not use the projects main issue tracker? > I do not have any separatist tendencies :-). The current state only reflects the "evolution" of the coastline. It started as a bunch of scripts for building GCC for HelenOS. At the beginning, I really did not care about other packages etc. and it was a set of small ugly scripts (opposite to the current situation when it is one big ugly script). I was also doing changes in libposix (that I tried to merge regularly) and I did not want to pollute the mainline with these helper scripts. Hence a separate repo. And since I expected it would be a (very) temporary solution, I really did not care whether I use the same versioning tool as the mainline or where would I host it. Regarding the issue tracker: I am not 100% sure that we want to pollute Trac with groups of tickets such "GCC does not compile on xy" yet. Just my opinion, I really do not care where the tickets are stored as long as I can see a list of them :-). The integration: I would prefer a separate repository just to keep mainline "clean" with strictly BSD code only. But maybe scripts working with GPL code are okay? Anyway, I do not want to end in the same situation as is currently with binutils, PCC and MSIM when they are part of the build process and probably no one builds them regularly as they slow down the building unacceptably. Hosting: I used mine because I simply had access to it. I agree that it would be definitely better to have it somewhere under helenos.org (at least I would get back those 500MB all the tarballs currently occupy) to give it a more "official" mark. I still consider coastline as an experimental script, but if we decide to make it somehow part of mainline, we should also discuss some related issues. First of all, what is the idea of packaging in HelenOS in general? At least in rough outlines such as approach like Gentoo vs Fedora vs Windows. Next issue: until installation to disk is possible, would the packages be installed during the build process or would they be downloaded/installed at runtime (btw, we have all the applications to do that, we just need to put them together)? A related question is some kind of automatic testing. It would be great to have an automatic re-generation of these packages + continuous integration that would at least verify that the compiled binary can be run (e.g. GCC prints version and compiles a hello-world). Even now (with only 10 ported packages), testing that ia32 works okay requires a non-trivial amount of time. I hope all this makes sense ;-). - Vojta > Best reards, > Jiri > > ---------- Původní zpráva ---------- > Od: Vojtech Horky <[email protected]> > Datum: 17. 12. 2013 > Předmět: [HelenOS-devel] GCC, Python and other goodies > > Hello, > just a short information regarding status of some ported software. > > First of all, I uploaded a lot of pre-compiled packages onto [1]. Just > download the tarball, unpack it into uspace/overlay, rebuild and you are > ready to go. > > I wrote few notes about the matrix on my blog [2] if you are interested in > details. The matrix is generated using my coastline scripts [3]. > > If you have some time to spare, I would be grateful if you would download > the packages and try them. Feel free to send bug reports either as replies > to this thread or directly to the issue tracker at GitHub [4]. > > Currently available binary packages include GCC + dependent libraries, > binutils, MSIM, fdlibm and Python (thanks to Zbigniew Halas). > > - Vojta > > [1] http://helenos.alisma.cz/coastline/matrix/ > [2] > http://vh.alisma.cz/blog/2013/12/08/helenos-coastline-updates-status-matrix/ > [3] https://github.com/vhotspur/coastline > [4] https://github.com/vhotspur/coastline/issues > > _______________________________________________ > HelenOS-devel mailing list > [email protected] > http://lists.modry.cz/listinfo/helenos-devel > > > _______________________________________________ > HelenOS-devel mailing list > [email protected] > http://lists.modry.cz/listinfo/helenos-devel > >
_______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
