Triode. Some feedback:
At times the logic of tick/untick method for install/remove with a single remove install button and a generic update over everything can get confusing in SOA. Several friends gave similar feedback. Perhaps it would be better to introduce action buttons: install/remove/purge/update on a per item basis. (we talked about "purge" as a new function earlier). A single Update option for the OS exclusive would be nice. Basically a "pacman -Syu" excluding SOA and SOA apps LMS/squeezlite/jivelite What's still missing then would be a dedicated "SOA" Package handling/update function. There's no SOA SW package entry option that would allow for SOA (soa-web) updates. Further I consider the current package ID layout pretty cryptic for a standard user. Why don't you use standard revs e.g. squeezelite "1.6.3" instead of "r119.b03b568-1" ? Perhaps you could also consider to rename the, at least to me, confusing overall "Update" - SOA section term to e.g. "SW Management" or similar. Cream of the crop would be an "update available" indication on a per item basis. The repo could be pinged at SOA boot to avoid a cron job. One more. Recently there were heavy updates on the Arch platform. gcc 4.9 was introduced instead of 4.8. At this point all the locally compiled SOA apps/kernel would also have be recompiled. How is this handled in SOA? Cheers ::: ' Touch Toolbox and more' (http://soundcheck-audio.blogspot.com) ::: by soundcheck ------------------------------------------------------------------------ soundcheck's Profile: http://forums.slimdevices.com/member.php?userid=34383 View this thread: http://forums.slimdevices.com/showthread.php?t=101624 _______________________________________________ unix mailing list [email protected] http://lists.slimdevices.com/mailman/listinfo/unix
