Sensor Operating System is an operating system for wireless sensor networks developped at UCLA. Sos 1.3 is the first non-beta release. I suggest dev-embedded for this package.
Created attachment 70918 [details] sos-1.3.ebuild
- please attach the license as plain text - first slot number is 0 - ${P} == ${MY_P}-${PV} in this case - src_unpack() is superfluous - What does "To develop applications with SOS as a user you must be a member of the sos group." mean exactly?
* The licence is spread all over the source code. Some parts are adapted from TinyOS and have the INTEL license. Other parts have a copyright notice at the beginning. (I will attach both in a minute) * I adjusted the ebuild according to the remarks in comment #2. In the meanwhile I also noticed in the sos tutorial that the preferred location for sos is sos-1.x instead of sos. I modified the ebuild to install to /opt/sos-1.x. * About the sos group: to develop applications that must run on sos, or to build the sample applications that are part of the source tree, one needs write permissions in the source tree. For that purpose I added a sos group and changed the permissions and ownerships of the source tree to make write access possible as a non-root user.
Created attachment 70934 [details] The INTEL license
Created attachment 70935 [details] the copyright notice present in some source files
Created attachment 70936 [details] sos-1.3.ebuild bis
This package does not meet the current criteria needed to be a viable candidate for the Portage tree since the upstream sources are no longer available at the location provided by the ebuild. This criteria is currently listed at the following URL: https://wiki.gentoo.org/wiki/Project:Proxy_Maintainers/Maintainer_Wanted Metric: Upstream status: Exists; "Package must still be available and fetchable (did it move to github, bitbucket, ...?)" If you (or another user) are still wanting this package to make it into the Portage tree please let us know by re-opening this bug and include a new usable upstream source. Sadly, until that time we cannot move forward with this ebuild. Tom D
