[jaffa]

Originally Posted by qgil

Thanks! I have sent a battery of questions to the relevant people and will come with answers asap. Others involved might even answer before me.

Thanks for these answers Quim, they're very helpful (as ever :-))

As for today, N950 and N9 have exactly the same security policy, and in fact are both wide open. Users only need to go to

Settings -> Applications -> Installations in order to Allow installations from non-Store sources.

If a user tries to install something out of the store a dialog appears telling her to go there to enable 3rd party installations. No need to get in developer mode, no need to go for open device.

(Emphasis added). This is good news, although it doesn't bode well from a manageable community support point of view ;-)

Are there currently plans for this security policy to change before release; or interest from carriers with subsidised devices to change it?

The browser, email app etc can also pass packages to the application manager. If a package comes alone without being tied to a repository and requiring additional packages, the installation will fail (of course). If it doesn't need dependencies but is not tied to a repository then it will miss potential updates (of course). However, I have installed packages from (internal 3rd party repositories aka experimental repos from Nokia teams) and then the information of the repository is also handled by the application manager, and new updates are announced when available.

So, to confirm, dependencies won't be resolved from the currently configured repositories for standalone debs?

One of the lessons that at least I had learned with the Maemo 5 iteration was the fact that having Extras pre-configured in the sales image put too much pressure on Extras itself. Like maemo.org Extras, apps.meego.com is a community driven repository and therefore it is healthier to detach it totally from a Nokia sales image. I'm happy to work for "equal opportunities" between Nokia Store and apps.meego.com apps once the user has decided to go apps.meego.com.

I think this was a good thing. If there are too many hurdles, and it's too easy to install random debs or run your own repository, we will have the issues that affected the 770 and Symbian - both technically and perception-wise (conflicts & a "look how few apps there are").

[bergie]

Originally Posted by jaffa

I think this was a good thing. If there are too many hurdles, and it's too easy to install random debs or run your own repository, we will have the issues that affected the 770 and Symbian - both technically and perception-wise (conflicts & a "look how few apps there are").

Agreed. Even though the QA process was felt to be heavy by some, in general having Extras enabled by default was a good thing. It meant a wealth of open source applications available for all users, and indeed avoided the "gazillion unmaintained repositories" problem that we saw with earlier Maemo devices.

[tekojo]

Originally Posted by pycage

From what I've gathered, we will have to depend on a special package from Nokia to enable the Community Repository on the device as this will probably be not possible in userland.

Just like on any other Linux system, adding repos is something that requires some more privileges than a normal user (not in developer mode) has.

I'm no longer in Nokia, but people are working on the easiest way to add the repository. (in essence a package that can add the community apps repo and on which the community client can depend on, and which is hosted by Nokia)

Edit: missed page 2 of the discussion. Never mind, carry on

[qgil]

Community application discovery client for Meego 1.2 Harmattan released as open source project http://gitorious.org/appbrowser

Now Sampo Savola (of eCoach fame), Niels Breet (of maemo.org/downloads fame) and other guys need to glue and fine tune the interaction between this client and apps.meego.com.

[bergie]

Originally Posted by qgil

Now Sampo Savola (of eCoach fame), Niels Breet (of maemo.org/downloads fame) and other guys need to glue and fine tune the interaction between this client and apps.meego.com.

I had a meeting with Sampo about that on Friday, and it is almost there.

On a bit later point it would make sense to merge this with Martin's Apps client, which has a lot of the features missing from this one.

[qgil]

As seen in my mailbox:

I receive yesterday information from Niels Breet that they have now repositories in place in following paths:

The repo url for the main Apps repository:
http://repo.pub.meego.com/repositori...armattan/Apps/

repo url for the Apps-testing repository:
http://repo.pub.meego.com/repositori.../Apps-testing/

and PGP pub key for these repositories

We will start to prepare key ring packages that will contain the path for these repositories & credentials -> I will contact our security team with this issue.

These should be added to sources.list.d as:
deb http://repo.pub.meego.com/repositori...armattan/Apps/ ./ deb http://repo.pub.meego.com/repositori.../Apps-testing/ ./

There will be two separate packages -> It would be good to have these two repos in separate enabler packages, so we can only enable the testing one for people who enable community QA and actually want to test.

The plan is that key ring packages are located for our application repository which device has always access.

[xfade]

Yes, some pieces of the puzzle are getting connected.

The Harmattan build target in community OBS is also available for developers who don't mind to look at hundreds of lines of warnings before the actual build starts. I'm still working on getting it a bit better, but at least this can give people a chance to start testing OBS builds for their app.

Documentation coming soon(ish)

[qgil]

Extracted from a long thread:

Originally Posted by jaffa

BTW, the getting started with OBS page now includes instructions for how to include PPA-style development repositories on Harmattan:

http://wiki.meego.com/Getting_started_with_OBS

X-Fade is still finishing up the next steps with the Community OBS for Harmattan, but it can be added in the "raw config" by copying (say) the raw config for :home:jaffa.

[jaffa]

Originally Posted by xfade

The Harmattan build target in community OBS is also available for developers who don't mind to look at hundreds of lines of warnings before the actual build starts. I'm still working on getting it a bit better, but at least this can give people a chance to start testing OBS builds for their app.

Until it becomes nicely available in the GUI; go to your project's Overview > Advanced > Raw config and add the following:

<repository name="Harmattan">  
  <path repository="Maemo.org_MeeGo_1.2_Harmattan_standard" project="MeeGo:1.2:Harmattan"/>  
  <arch>armv7el</arch>  
</repository>

It can also be added by going to your project's Overview > Repositories > Add > Advanced and start typing "harmattan" in the first field. Once autocompleted, untick i586 and armv8el, and tick armv7el.

Once added, this should trigger a rebuild of packages in that project. See Quim's above link for more information on how to install the resulting repository.

Harmattan in COBS is still in development. Things may go wibbly, so don't expect high levels of SLA yet.

[rzr]

I confirm It's working I built connect-proxy , is there a document to promote it to a common respo , btw does install files are still useful ?