Hello, I updated debian/control file to take into account Peter's comments.About the dependencies, this program was this first I made using autoconf and automake, so it is likely I forgot stuff. I guess the proper way to test for it is by a chrooted environment ? I have little experience with that too, but I will take a look (I'm here to learn :-) )
Thanks all for your comments/revisions ! Yves On 04/14/2013 01:22 AM, peter green wrote:
Anton Gladky wrote:IMO if you don't have access to a peice of hardware you probablly shouldn't be sponsoring hardware specific packages for it.I would agree with that. But there is a problem of package building. It means, we can upload only the binary-version (source-based uploads are still not implemented in Debian unfortunately), which was built on armel, what is not always simple or difficult. Also if the package will require NMU, one need to find such machine to build a package to upload.If an emergency NMU is needed and the original sponsor who has the hardware is not arround then there is a porterbox available.BTW another thing I noticed was the package has virtually no build-dependecnies, is that really the case or are they missing.@Peter, would you agree to review/upload the package directly to Raspbian?Unfortunately I don't realy have the time for reviewing packages at the moment. Raspbian is mostly a one man show at the moment (mike is still arround but not very active). I plan to try and recruit more developers later but I want to get us migrated onto new infrastructure first). In any case debian armel does run on the Pi so having it in armel makes sense.