<div dir="ltr"><div><div>I have no major comments on dependencies, provided that:<br>a) they are strictly @ app-level, ie no OS dependencies (unless hacked)<br></div>b) they do not break after device updates<br></div>c) they are transparent to the user (except the eventual download part)<br>
<br>Best,<br>tortoisedoc<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Nov 6, 2013 at 7:51 PM, Andrey Kozhevnikov <span dir="ltr"><<a href="mailto:coderusinbox@gmail.com" target="_blank">coderusinbox@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">lol, really? you think developing own libraries sucks? arent you developed something really BIG?<div class="HOEnZb"><div class="h5">
<br>
<br>
On 06.11.2013 23:47, <a href="mailto:khertan@khertan.net" target="_blank">khertan@khertan.net</a> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
An analogy with boat about apps including his own libs :<br>
<br>
<a href="https://mobile.twitter.com/usmanm/status/388407160159211520/photo/1?screen_name=usmanm#!/usmanm/status/388407160159211520/photo/1?screen_name=usmanm" target="_blank">https://mobile.twitter.com/<u></u>usmanm/status/<u></u>388407160159211520/photo/1?<u></u>screen_name=usmanm#!/usmanm/<u></u>status/388407160159211520/<u></u>photo/1?screen_name=usmanm</a><br>
<br>
:p<br>
<br>
--<br>
Benoît HERVIER - <a href="http://khertan.netLe" target="_blank">http://khertan.netLe</a> 06/11/13 18:33 Marcin M. a écrit :<br>
And somehow Debian and Ubuntu and ... do well it with real depends...<br>
<br>
<br>
<br>
--Marcin<br>
<br>
<br>
<br>
<br>
2013/11/6 Marcin M. <<a href="mailto:marmistrzmar@gmail.com" target="_blank">marmistrzmar@gmail.com</a>><br>
<br>
If everything handled correctly (assuming no 3rd party lib updates) what bad can happen?<br>
<br>
<br>
<br>
-- Marcin<br>
<br>
<br>
<br>
<br>
2013/11/6 Martin Grimme <<a href="mailto:martin.grimme@gmail.com" target="_blank">martin.grimme@gmail.com</a>><br>
<br>
Hi,<br>
<br>
2013/11/6, 郭云鹤 <<a href="mailto:guoyunhebrave@gmail.com" target="_blank">guoyunhebrave@gmail.com</a>>:<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
i think every app should be independent. apps' dependence caused many<br>
problems.<br>
</blockquote>
<br>
I think the same. While having deps and libraries and everything is<br>
cool from a Linuxer's point of view, it will give a bad user<br>
experience and just cry for breaking things when updating the OS or<br>
other apps.<br>
<br>
You can either try to get the library into Nemo, or include it in your<br>
package or link to it statically. Those few kbytes wasted by this<br>
approach should be no real problem, but worth it, if it improves the<br>
user's experience and happiness with Sailfish devices.<br>
<br>
I remember people crying they could not update their N900 because of<br>
some library dependencies. Don't let this happen again.<br>
1337 Linux h4x0rz in need of obscure libs and stuff will always find a<br>
workaround to fulfill their needs, e.g. with 3rd party repositories.<br>
:)<br>
<br>
Keep in mind that Sailfish wants to be attractive to regular users and<br>
user experience should be highly valued.<br>
<br>
<br>
My 2 cents,<br>
Martin<br>
<br>
<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
郭云鹤(Guo Yunhe)<br>
<a href="http://guoyunhe.me/" target="_blank">http://guoyunhe.me/</a><br>
在 2013-11-7 上午12:13，"Marcin M." <<a href="mailto:marmistrzmar@gmail.com" target="_blank">marmistrzmar@gmail.com</a>>写道：<br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
It's not a pity when it comes to libraries. It is when you create a<br>
modular app ;) - divided into packages. But if there was an<br>
in-app-purchase<br>
system, it wouldn't be so bad :)<br>
<br>
--<br>
Marcin<br>
<br>
<br>
2013/11/6 Mohammed Hassan <<a href="mailto:mohammed.hassan@jollamobile.com" target="_blank">mohammed.hassan@jollamobile.<u></u>com</a>><br>
<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
I don't see it as a pity. I see it as an opportunity for everyone<br>
to push their libraries and stuff to mer/nemo/sailfish.<br>
<br>
An advantage of SailfishOS is that everyone can contribute and have<br>
their<br>
own applications, libraries and tools there.<br>
<br>
Just my 0.02<br>
<br>
Cheers,<br>
<br>
On Wed, Nov 06, 2013 at 05:06:58PM +0100, Marcin M. wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi,<br>
Thanks! Well, it's a pity ;(<br>
Regards,<br>
<br>
--<br>
Marcin<br>
2013/11/6 Jonni Rainisto <[1]<a href="mailto:jonni.rainisto@jolla.com" target="_blank">jonni.rainisto@jolla.com</a>><br>
<br>
Hi,<br>
AFAIK. Currently you can only depend on mer/nemomobile packages, you<br>
cannot depend on store packages.<br>
re, Jonni<br>
______________________________<u></u>______________________________<u></u>______<br>
<br>
From: [2]<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.<u></u>sailfishos.org</a><br>
[[3]<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.<u></u>sailfishos.org</a>] on behalf of Marcin M.<br>
[[4]<a href="mailto:marmistrzmar@gmail.com" target="_blank">marmistrzmar@gmail.com</a>]<br>
Sent: Wednesday, November 06, 2013 5:34 PM<br>
To: Sailfish OS Developers<br>
Subject: Re: [SailfishDevel] Jolla Harbour and Jolla Store<br>
And what about in-app-store depends? (Free app, paid databases,<br>
databases depend on the free app)<br>
--<br>
Marcin<br>
2013/11/6 Andrey Kozhevnikov <[5]<a href="mailto:coderusinbox@gmail.com" target="_blank">coderusinbox@gmail.com</a>><br>
<br>
Good point, thanks!<br>
<br>
On 06.11.2013 18:30, Jonni Rainisto wrote:<br>
<br>
And if some good library is missing, and you are willing to maintain<br>
the library, feel free trying to get it added to Mer/Nemomobile side<br>
(after that you can depend against it).<br>
re, Jonni<br>
______________________________<u></u>__________<br>
From: [6]<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.<u></u>sailfishos.org</a><br>
[[7]<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.<u></u>sailfishos.org</a>] on behalf of Jonni Rainisto<br>
[[8]<a href="mailto:jonni.rainisto@jolla.com" target="_blank">jonni.rainisto@jolla.com</a>]<br>
Sent: Wednesday, November 06, 2013 2:27 PM<br>
To: Sailfish OS Developers<br>
Subject: Re: [SailfishDevel] Jolla Harbour and Jolla Store<br>
HI,<br>
AFAIK, uploading libraries to store is forbidden, you can only<br>
depend on common mer/nemomobile libraries in .spec/rpm Requires<br>
field.<br>
re, Jonni<br>
______________________________<u></u>__________<br>
From: [9]<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.<u></u>sailfishos.org</a><br>
[[10]<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.<u></u>sailfishos.org</a>] on behalf of Andrey<br>
Kozhevnikov [[11]<a href="mailto:coderusinbox@gmail.com" target="_blank">coderusinbox@gmail.com</a>]<br>
Sent: Wednesday, November 06, 2013 1:40 PM<br>
To: [12]<a href="mailto:devel@lists.sailfishos.org" target="_blank">devel@lists.sailfishos.org</a><br>
Subject: Re: [SailfishDevel] Jolla Harbour and Jolla Store<br>
Please more information about Harbour:<br>
- it can accept only single files, means i cant upload some<br>
libraries,<br>
required as depends for my appliction?<br>
- does it acts as repository?<br>
On 06.11.2013 17:06, Karl Granström wrote:<br>
<br>
Ahoy all,<br>
Today we're launching Jolla Harbour <[13]<a href="http://harbour.jolla.com" target="_blank">harbour.jolla.com</a>>, the<br>
portal for submitting applications to the Jolla Store.<br>
You can submit and manage your applications. Consumers will be able<br>
to install them directly from their Jolla phones.<br>
Here are some details about Jolla Harbour:<br>
Joining and logging into Jolla Harbour:<br>
Joining is free! You can create a Jolla account from the Jolla<br>
Harbour landing page ([14]<a href="http://harbour.jolla.com" target="_blank">harbour.jolla.com</a>) or if you have<br>
pre-ordered your Jolla phone, you have everything you need to get<br>
started. To manage your account details, please visit<br>
[15]<a href="http://account.jolla.com" target="_blank">account.jolla.com</a>.<br>
Support for Sailfish and Android™ applications:<br>
You can submit both Sailfish and Android™ applications to Jolla<br>
Harbour. The submission process is the same.<br>
Start with free applications:<br>
At launch, the Jolla Harbour and Jolla Store will support only free<br>
applications. We are working hard to enable payment solutions and we<br>
will keep you posted about these capabilities as they develop.<br>
Binary package naming:<br>
You will receive naming guidelines when you upload the binary<br>
package to Jolla Harbour. You can also find guidelines on versioning<br>
at [16]<a href="http://semver.org" target="_blank">http://semver.org</a>.<br>
Preparing your metadata:<br>
Jolla Harbour needs to know a few things about your app:<br>
- An app icon for the Store (86x86px, png) (Current SDK supports<br>
90x90px images; more details to follow soon)<br>
- 1-3 screenshots (540x960px, png or jpg)<br>
- An optional Cover image for your Store page (516x252px, png or<br>
jpg)<br>
Submission process:<br>
To submit your application to Jolla Harbour, fill in the metadata<br>
for it and upload the binary and required images. After you have<br>
submitted your app, Jolla will start Quality Assurance testing.<br>
Quality Assurance testing:<br>
Jolla will perform QA testing on your applications on real Jolla<br>
devices. We will get back to you with feedback on your app within a<br>
few days. You will be notified on the QA results via the email<br>
address you have registered to your Jolla account.<br>
If you encounter any issues, please contact us by email,<br>
[17]<a href="mailto:developer-care@jolla.com" target="_blank">developer-care@jolla.com</a>, or report them to the Sailfish<br>
developers mailing list at devel at [18]<a href="http://lists.sailfishos.org" target="_blank">lists.sailfishos.org</a>.<br>
Happy hacking!<br>
The Jolla Store Team<br>
______________________________<u></u>_________________<br>
SailfishOS.org Devel mailing list<br>
<br>
______________________________<u></u>_________________<br>
SailfishOS.org Devel mailing list<br>
______________________________<u></u>_________________<br>
SailfishOS.org Devel mailing list<br>
______________________________<u></u>_________________<br>
SailfishOS.org Devel mailing list<br>
<br>
______________________________<u></u>_________________<br>
SailfishOS.org Devel mailing list<br>
<br>
______________________________<u></u>_________________<br>
SailfishOS.org Devel mailing list<br>
<br>
References<br>
<br>
1. mailto:<a href="mailto:jonni.rainisto@jolla.com" target="_blank">jonni.rainisto@jolla.<u></u>com</a><br>
2. mailto:<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.<u></u>sailfishos.org</a><br>
3. mailto:<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.<u></u>sailfishos.org</a><br>
4. mailto:<a href="mailto:marmistrzmar@gmail.com" target="_blank">marmistrzmar@gmail.com</a><br>
5. mailto:<a href="mailto:coderusinbox@gmail.com" target="_blank">coderusinbox@gmail.com</a><br>
6. mailto:<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.<u></u>sailfishos.org</a><br>
7. mailto:<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.<u></u>sailfishos.org</a><br>
8. mailto:<a href="mailto:jonni.rainisto@jolla.com" target="_blank">jonni.rainisto@jolla.<u></u>com</a><br>
9. mailto:<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.<u></u>sailfishos.org</a><br>
10. mailto:<a href="mailto:devel-bounces@lists.sailfishos.org" target="_blank">devel-bounces@lists.<u></u>sailfishos.org</a><br>
11. mailto:<a href="mailto:coderusinbox@gmail.com" target="_blank">coderusinbox@gmail.com</a><br>
12. mailto:<a href="mailto:devel@lists.sailfishos.org" target="_blank">devel@lists.sailfishos.<u></u>org</a><br>
13. <a href="http://harbour.jolla.com/" target="_blank">http://harbour.jolla.com/</a><br>
14. <a href="http://harbour.jolla.com/" target="_blank">http://harbour.jolla.com/</a><br>
15. <a href="http://account.jolla.com/" target="_blank">http://account.jolla.com/</a><br>
16. <a href="http://semver.org/" target="_blank">http://semver.org/</a><br>
17. mailto:<a href="mailto:developer-care@jolla.com" target="_blank">developer-care@jolla.<u></u>com</a><br>
18. <a href="http://lists.sailfishos.org/" target="_blank">http://lists.sailfishos.org/</a><br>
______________________________<u></u>_________________<br>
SailfishOS.org Devel mailing list<br>
</blockquote>
______________________________<u></u>_________________<br>
SailfishOS.org Devel mailing list<br>
<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
SailfishOS.org Devel mailing list<br>
<br>
</blockquote></blockquote>
______________________________<u></u>_________________<br>
SailfishOS.org Devel mailing list<br>
<br>
<br>
<br>
<br>
______________________________<u></u>_________________<br>
SailfishOS.org Devel mailing list<br>
</blockquote>
<br>
______________________________<u></u>_________________<br>
SailfishOS.org Devel mailing list</div></div></blockquote></div><br></div>