Hi everyone! I would like to know how Harbour will handle possible applications conflicts. Case 1 - Titles are the same: Dev1 submits application called "Trains Europe" about history of europe trains with binary "trains_1.0.0_armv7hl.rpm" Dev2 submits application called "Trains Europe" about online timetable for train transport called "trainseurope_1.0.0_armv7hl.rpm".
Case 2 - Binary names are the same: Dev1 submits application called "Trains Europe History" about history of europe trains with binary "trainseurope_1.0.0_armv7hl.rpm" Dev2 submits application called "Trains Europe Timetable" about online timetable for train transport called "trainseurope_1.0.0_armv7hl.rpm". Case 3 - Exact same package (opensource) from developers: Dev1 submits application called "Trains Europe Timetable" about online timetable for train transport for France and Germany with binary "trainseurope_1.5.0_armv7hl.rpm" Dev2 submits application called "Trains Europe Timetable" about online timetable for train transport for France and Italy called "trainseurope_1.3.7_armv7hl.rpm". Both packages are based on some opensource application but dev implement own updates to package.. The 3rd case is most valuable since, lots of apps are being ported and submitted to harbour not by primary devs, but by support teams. For example real application Tweetian. Dicksonleong said that he will not develop new features at Tweetian any more, only bugfixes. Sailfish port exists here: https://github.com/veskuh/Tweetian/tree/sailfish-port and here https://github.com/siteshwar/Tweetian/tree/sailfish-port When Jolla will be released may be Dicksonleong will change his mind and start developing application once again, but seems like siteshwar's(most active port) binary will be already published. Also ports are not 100% equal, different features can be implemented based on requests to maintainers. Regards, Basil. -- Semuonov Basil --- Line of cut --- Linux everywhere...
_______________________________________________ SailfishOS.org Devel mailing list
