Hi. 2015-02-10 21:30 GMT+01:00 Dominik Taborsky <[email protected]>:
> How about a package manager and/or a package repo? > I am not sure that full-fledged package manager is a good GSoC project. This is rather thesis topic because you cannot start coding right away. You need to think about how to handle things such as multiple versions of the same package or approach to software that does its own packaging (for example, Ruby and its gems). Plus plenty of details regarding atomicity of updates, rollbacking or the organization of the package database. I think this would deserve some more discussions here on the ML. But if you have something ready, go ahead :-). > On 02/10/2015 09:21 PM, Jakub Jermar wrote: > >> - Port Git to HelenOS >> - Extend BeagleBoard support (BeagleBoard Black, drivers) >> - Extend RaspberryPi support (drivers, the new RPi) >> - GUI improvements (toolkit, get rid of floats, there is a list of >> things to hack on the GUI somewhere) >> - USB ethernet driver >> - USB serial driver >> >> Comments? >> > I would like to see there continuous testing. There is already the code that accompanied Martin's thesis but AFAIK it does not have a simple way to express more complex things, such as: "type ls and verify words app, srv and src are in the output". That is, something that could run QEMU, capture its screen, OCR-it and then check it. Another point is in making this easily deployable in Jenkins or similar tool. One more thing came to my mind. It would be nice to have more "first-patch" tickets there [1]. If you know about something simple and reasonable, do not hesitate to create such ticket ;-). @JJ: you are listed as the owner of most of these tickets probably because you are the default owner for libc. Would you mind if I orphan these? - Vojta [1] http://trac.helenos.org/query?keywords=~first-patch&status=!closed&order=priority
_______________________________________________ HelenOS-devel mailing list [email protected] http://lists.modry.cz/listinfo/helenos-devel
