|
2013-07-18
, 09:33
|
|
Posts: 747 |
Thanked: 2,370 times |
Joined on May 2012
@ Moscow, Russia
|
#72
|
What do you thing to add a field "Compatibility" or something in app description just to know about PR1.x and n9xx compatibility ?
(Maybe a table phone/PR version ???)
|
2013-07-18
, 09:41
|
Moderator |
Posts: 5,320 |
Thanked: 4,464 times |
Joined on Oct 2009
|
#73
|
With some sadness we announce that the Nokia Developer Projects service (https://projects.developer.nokia.com) will be discontinued in the following months (due to ongoing trend of low activity and increasing costs). Please backup any project data you wish to save as soon as possible (ideally within the next few weeks). After the service has been stopped all unsaved data will be lost!
Thank you for using Projects and being part of our community!
Note that all the other community services, including discussion boards and wiki, will remain available for your future use and enjoyment.
How can I migrate my repositories somewhere else?
For git:
1. Make sure that you’ve pulled the latest revision of the repository you wish to move. You can usually achieve this by running the following command in your local repository:
git fetch origin
2. Create an empty git repository somewhere else.
3. Add the newly created empty repository as a new remote by running the following command:
git remote add new_repo https://$LOCATION_OF_NEW_REPO
4. In the root directory of the repository, run the command:
git push --tags new_repo refs/remotes/origin/*:refs/heads/*
5. You can now clone the new repository and start using it. It should have the entire history of the old one.
For mercurial:
1. Make sure that you’ve pulled the latest revision of the repository you wish to move.
2. Create an empty hg repository somewhere else.
3. Edit the .hg/hgrc file of the repository you wish to move adding the following line to the [paths] section:
new_repo = https://$LOCATION_OF_NEW_REPO
4. In the root directory of the repository, run the command:
hg push new_repo
5. You can now clone the new repository and start using it. It should have the entire history of the old one.
For subversion:
1. Download and install rsvndump on your local machine: http://rsvndump.sourceforge.net
2. Create a subversion dump file by running:
rsvndump --username $username --password $password --keep-revnums https://$PATH_TO_MULTIPROJECT_REPO > repository.dump
3. (Optional) If you need to filer out some cruft from the repository before importing it somewhere else, this should be done now. The tool svndumpsanitizer is recommended for the job. http://miria.linuxmaniac.net/svndumpsanitizer
4. Set up an empty svn repository somewhere else.
5. Transfer the dump file to the new server.
6. Import (or have your friendly new system admin import) the dump file by running:
svnadmin load /path/to/new/repo < repository.dump
7. You can now check out the new repository and start using it. It should have the entire history of the old one (minus the stuff you optionally excluded with svndumpsanitizer).
|
2013-07-18
, 14:14
|
|
Posts: 1,012 |
Thanked: 817 times |
Joined on Jul 2007
@ France
|
#74
|
not all paid apps are non-libre, and not all gratis apps are libre. there are counterexamples for both in the ovi store.
important thing is to check the LICENSE; if it allows for redistribution, regardless of price, then youre good.
{apache, mit, bsd, gpl}
open up the debian in an archive managing app {e.g.: file-roller}, and look for text files {e.g.: README or COPYING} and find the license. if you cant find anything, assume you have no rights, or email the developer asking for license information.
The Following 4 Users Say Thank You to Khertan For This Useful Post: | ||
|
2013-07-19
, 12:29
|
Posts: 84 |
Thanked: 62 times |
Joined on Jun 2013
|
#75
|
|
2013-07-19
, 12:34
|
|
Posts: 6,436 |
Thanked: 12,701 times |
Joined on Nov 2011
@ Ängelholm, Sweden
|
#76
|
|
2013-07-19
, 15:53
|
|
Posts: 747 |
Thanked: 2,370 times |
Joined on May 2012
@ Moscow, Russia
|
#77
|
Who's have rights to publish apps on openrepos? E.g. MeeCast has already published twice while the developer himself has nothing to do with it. Who's gonna be control situations like this? I don't mean any kind of copyleft violations but just to avoid confusion with the versions. One MeeCast version is 0.7 and other version is 0.7.3
|
2013-07-19
, 16:14
|
Posts: 84 |
Thanked: 62 times |
Joined on Jun 2013
|
#78
|
That's why every publisher have own repository. When you enable publisher repository, you can install app versions that this publisher distributes(uploaded to the openrepos).
And that's why there is no any "global"-single repository.
If this is "one-version-repository" then application will never get any update (i.e. like imported appsformeego applications). and if developer hosts here, then you get all new versions of applications.
Of course this take place if apps dont violate any owners/developers rights.
And cherry-picking apps from repository into own mixed repository should prevent (atleast up to 90%) of re-uploads of same application.
|
2013-07-21
, 15:07
|
|
Posts: 1,348 |
Thanked: 1,863 times |
Joined on Jan 2009
@ fr/35/rennes
|
#79
|
|
2013-07-26
, 12:38
|
|
Posts: 747 |
Thanked: 2,370 times |
Joined on May 2012
@ Moscow, Russia
|
#80
|
The Following 11 Users Say Thank You to Custodian For This Useful Post: | ||
What do you thing to add a field "Compatibility" or something in app description just to know about PR1.x and n9xx compatibility ?
(Maybe a table phone/PR version ???)
Thanks !