Active Topics
-
Firefox with Leste (10)
to Maemo 7 / Leste by teroyk - 3 days ago - more...
|
2011-12-05
, 15:53
|
|
Posts: 1,298 |
Thanked: 2,277 times |
Joined on May 2011
|
#42
|
I have some questions about apps.formeego.org, which weren't answered by anyone so far. See starting from here:
http://forum.meego.com/showthread.php?p=36018#post36018
In short, why can't dependencies on libraries be specified in it?
Last edited by shmerl; 2011-12-05 at 16:07.
http://forum.meego.com/showthread.php?p=36018#post36018
In short, why can't dependencies on libraries be specified in it?
Last edited by shmerl; 2011-12-05 at 16:07.
 |
|
2011-12-05
, 16:00
|
|
Posts: 1,038 |
Thanked: 1,408 times |
Joined on Feb 2010
@ London
|
#43
|
I am unable to 'rate' a downloaded App. Already have discovered some useful feedback for the developer so would like to share that too.
| The Following User Says Thank You to afaq For This Useful Post: | ||
|
|
2011-12-06
, 08:33
|
|
Posts: 152 |
Thanked: 620 times |
Joined on Mar 2008
@ Netherlands
|
#44
|
Originally Posted by shmerl
Short answer: To prevent a dependency mess, we started with 'clean' builds against the sdk only.
I have some questions about apps.formeego.org, which weren't answered by anyone so far. See starting from here:
http://forum.meego.com/showthread.php?p=36018#post36018
In short, why can't dependencies on libraries be specified in it?
Longer answer: Of course we should try to harness the power of shared libraries etc. To prevent people from randomly uploading dependencies and not caring if it breaks other packages, we need to come up with a way to do this properly.
My idea is to have a separate repository where shared libraries are managed (maybe even with a staging repository where we can test breakage when new versions are introduced). We can go for package maintainers per package or a group of interested people who manage the repository.
For this to not become a mess, we need to have a clear policy and good communication between maintainers.
I intend to come up with at proposal on the wiki this week. I'll ask for input/ideas after that. And of course ask for volunteers
__________________
http://maemo.org/profile/view/xfade/ - maemo.org webmaster Apps.formeego.org (Apps for N9)
http://maemo.org/profile/view/xfade/ - maemo.org webmaster Apps.formeego.org (Apps for N9)
| The Following 10 Users Say Thank You to X-Fade For This Useful Post: | ||
|
|
2011-12-06
, 08:35
|
|
Posts: 152 |
Thanked: 620 times |
Joined on Mar 2008
@ Netherlands
|
#45
|
Originally Posted by afaq
I guess you are trying this in the client itself? Feedback is not implemented there yet.
I am unable to 'rate' a downloaded App. Already have discovered some useful feedback for the developer so would like to share that too.
Feedback and rating on http://apps.formeego.org should work though.
__________________
http://maemo.org/profile/view/xfade/ - maemo.org webmaster Apps.formeego.org (Apps for N9)
http://maemo.org/profile/view/xfade/ - maemo.org webmaster Apps.formeego.org (Apps for N9)
|
|
2011-12-06
, 10:45
|
|
Posts: 1,269 |
Thanked: 3,961 times |
Joined on May 2011
@ Brazil
|
#46
|
Originally Posted by X-Fade
Thanks for the answer and the work on apps.formeego.org.
Short answer: To prevent a dependency mess, we started with 'clean' builds against the sdk only.
Longer answer: Of course we should try to harness the power of shared libraries etc. To prevent people from randomly uploading dependencies and not caring if it breaks other packages, we need to come up with a way to do this properly.
My idea is to have a separate repository where shared libraries are managed (maybe even with a staging repository where we can test breakage when new versions are introduced). We can go for package maintainers per package or a group of interested people who manage the repository.
For this to not become a mess, we need to have a clear policy and good communication between maintainers.
I intend to come up with at proposal on the wiki this week. I'll ask for input/ideas after that. And of course ask for volunteers
I think it is important to the end user :
1) install in the same way softwares with or without dependencies;
2) also install libraries / softwares without icons / softwares CLI (Command Line Interface), there are some waiting for repositories, for example Python Harmattan softwares from the community;
3) easily see the testing softwares from the Apps.ForMeeGo application (without need to go to a web site and install a .deb to enable it).
I now have 7 packages for the case (2), and 3 softwares with GUI and dependencies until the end of this month, all waiting for Apps.Formeego.
__________________
Python, C/C++, Qt and CAS developer. For Maemo/MeeGo/Sailfish :
Integral, Derivative, Limit - calculating mathematical integrals, derivatives and limits. SymPy - Computer Algebra System.
MatPlotLib - 2D & 3D plots in Python. IPython - Python interactive shell.
-- My blog about mobile & scientific computing ---
Sailfish : Sony Xperia X, Gemini, Jolla, Jolla C, Jolla Tablet, Nexus 4. Nokia N9, N900, N810.
Python, C/C++, Qt and CAS developer. For Maemo/MeeGo/Sailfish :
Integral, Derivative, Limit - calculating mathematical integrals, derivatives and limits. SymPy - Computer Algebra System.
MatPlotLib - 2D & 3D plots in Python. IPython - Python interactive shell.
-- My blog about mobile & scientific computing ---
Sailfish : Sony Xperia X, Gemini, Jolla, Jolla C, Jolla Tablet, Nexus 4. Nokia N9, N900, N810.
|
|
2011-12-06
, 15:23
|
|
Posts: 1,298 |
Thanked: 2,277 times |
Joined on May 2011
|
#47
|
Thanks for the clarification X-Fade! What is considered a clean build against Harmattan and Nemo at the moment? One depending on Harmattan SDK or Mer packages? Will the additional repo with dependencies need to be maintained for Harmattan and Nemo separately?
| The Following 2 Users Say Thank You to shmerl For This Useful Post: | ||
|
|
2011-12-06
, 15:38
|
|
Posts: 152 |
Thanked: 620 times |
Joined on Mar 2008
@ Netherlands
|
#48
|
Clean dependencies means that you don't need any other packages from your home project (Or the project the package is building in)
So once you need to upload a lib first to get your package to build, then you are out of luck in the current setup. Unless you statically link against it. That is a possibility too, but that is not an optimal one.
For extra dependencies to work, we need to address the things I mentioned in my previous posts.
So once you need to upload a lib first to get your package to build, then you are out of luck in the current setup. Unless you statically link against it. That is a possibility too, but that is not an optimal one.
For extra dependencies to work, we need to address the things I mentioned in my previous posts.
__________________
http://maemo.org/profile/view/xfade/ - maemo.org webmaster Apps.formeego.org (Apps for N9)
http://maemo.org/profile/view/xfade/ - maemo.org webmaster Apps.formeego.org (Apps for N9)
| The Following 4 Users Say Thank You to X-Fade For This Useful Post: | ||
|
|
2011-12-06
, 18:00
|
|
Posts: 1,298 |
Thanked: 2,277 times |
Joined on May 2011
|
#49
|
I was asking more about the difference between Harmattan and Nemo in regards to what system packages will be expected by default (since you mentioned SDK packages) and how the proposed repositories where additional dependencies will be added later are going to work out in practice for both (since apps.formeego.org was intended to cater for both systems). Just an example, let's say boost will be added to the new repository. So it'll need to be maintained for all proposed targets? (Harmattan & Nemo at least?).
| The Following User Says Thank You to shmerl For This Useful Post: | ||
|
|
2011-12-09
, 10:23
|
|
Posts: 152 |
Thanked: 620 times |
Joined on Mar 2008
@ Netherlands
|
#50
|
Originally Posted by shmerl
The repositories would be separate as they have a different target. That is not to say the same packages can't be in both of them. There is the added complication that Harmattan and Nemo are using different packaging. So yes, the shared extra dependencies should be maintained for each target separately.
I was asking more about the difference between Harmattan and Nemo in regards to what system packages will be expected by default (since you mentioned SDK packages) and how the proposed repositories where additional dependencies will be added later are going to work out in practice for both (since apps.formeego.org was intended to cater for both systems). Just an example, let's say boost will be added to the new repository. So it'll need to be maintained for all proposed targets? (Harmattan & Nemo at least?).
__________________
http://maemo.org/profile/view/xfade/ - maemo.org webmaster Apps.formeego.org (Apps for N9)
http://maemo.org/profile/view/xfade/ - maemo.org webmaster Apps.formeego.org (Apps for N9)
| The Following 4 Users Say Thank You to X-Fade For This Useful Post: | ||
Really like what I see so far in the repos.
Graphic and Calligraphy Designer
check out my site www.afaqali.com