Community Repository

From Openmoko

(Difference between revisions)
Jump to: navigation, search
(Add repository by installing repository package)
m (Add repository by installing repository package)
Line 42: Line 42:
  
 
= Add Repository on Neo =  
 
= Add Repository on Neo =  
== Add repository by installing repository package ==
+
== Add repositories by installing repository packages ==
(Warning: It need the image after ASU)
+
* The community-repository is installed by default in [[ASU]].
* The community-repository is installed in ASU by default now
+
  
 
== Add repository manually ==
 
== Add repository manually ==

Revision as of 17:01, 27 July 2008

--Tick 03:46, 23 June 2008 (UTC)This page may change rapidly recently. Alpha 0.1.0

Contents

Community Repository

There is a community repository that every one can release your projects on Neo.

Sites

The Repository: http://downloads.openmoko.org/community-repository/

The mailing list: http://lists.openmoko.org/mailman/listinfo/community-repository

How to release packages

You can release your package with ipk file.

Package Tags

If you want your package to be shown on Assassin, please add tag message on your package.

Category Tag
Communication group::communication
Development group::programming
Games group::games
Maps group::maps
Miscellaneous group::unknown
Network group::network
Repos group::repos
  • For OE user, please adding the Tag by adding one line in your bb file

For example:

PKG_TAGS_${PN} = "group::games"

Add Repository on Neo

Add repositories by installing repository packages

  • The community-repository is installed by default in ASU.

Add repository manually

  • create a file, here we call it community-repos.conf
> echo "arch community-repos 50" > community-repos.conf
> echo "src community-repos http://downloads.openmoko.org/community-repository/" >> community-repos.conf
  • connect to your Neo with USB
> sudo ifconfig usb0 192.168.0.200
> scp community-repos.conf root@192.168.0.202:/etc/opkg/
  • refresh the opkg metadata database
> ssh root@192.168.0.202 
after connecting to Neo
> opkg update

We need your help

We need reviewers who review the new packages. If you want to help please send e-mail to the mailing list community-repository@lists.openmoko.org .


Before applying to be a reviewer, please make sure you have.

  • an account on projects.openmoko.org
  • had put ssh public key on projects.openmoko.org
  • knowing how to use svn
  • knowing how to use opkg
  • knowing how to do software test

Openmoko appreciate your help.

 Current Reviewers
 Tick

Review Packages

The reviewer will check if there have new packages on the mailing list. If you are reviewer and want to review that package

  • reply that mail, and say you want to review that
  • check if the package follows the policy
  • download the package on projects.openmoko.org
  • install that package to see if
    • installable?
    • executable able?
    • functions the claimed works actually works?
    • If it do something bad?
    • uninstall it and see if everything still ok?
  • if the package is okay, put the package in this file and the package will shown next day.

Review Policy

  • Packages in this repository shall not in OM repository
  • Program shall not collect user information and send to others unless it has very clear notification
  • Program shall not destroy the system
  • All packages shall be run-able on Neo
  • The package file name should refer which version of the project is compiled.
Personal tools

--Tick 03:46, 23 June 2008 (UTC)This page may change rapidly recently. Alpha 0.1.0

Community Repository

There is a community repository that every one can release your projects on Neo.

Sites

The Repository: http://downloads.openmoko.org/community-repository/

The mailing list: http://lists.openmoko.org/mailman/listinfo/community-repository

How to release packages

You can release your package with ipk file.

Package Tags

If you want your package to be shown on Assassin, please add tag message on your package.

Category Tag
Communication group::communication
Development group::programming
Games group::games
Maps group::maps
Miscellaneous group::unknown
Network group::network
Repos group::repos
  • For OE user, please adding the Tag by adding one line in your bb file

For example:

PKG_TAGS_${PN} = "group::games"

Add Repository on Neo

Add repositories by installing repository packages

  • The community-repository is installed by default in ASU.

Add repository manually

  • create a file, here we call it community-repos.conf
> echo "arch community-repos 50" > community-repos.conf
> echo "src community-repos http://downloads.openmoko.org/community-repository/" >> community-repos.conf
  • connect to your Neo with USB
> sudo ifconfig usb0 192.168.0.200
> scp community-repos.conf root@192.168.0.202:/etc/opkg/
  • refresh the opkg metadata database
> ssh root@192.168.0.202 
after connecting to Neo
> opkg update

We need your help

We need reviewers who review the new packages. If you want to help please send e-mail to the mailing list community-repository@lists.openmoko.org .


Before applying to be a reviewer, please make sure you have.

  • an account on projects.openmoko.org
  • had put ssh public key on projects.openmoko.org
  • knowing how to use svn
  • knowing how to use opkg
  • knowing how to do software test

Openmoko appreciate your help.

 Current Reviewers
 Tick

Review Packages

The reviewer will check if there have new packages on the mailing list. If you are reviewer and want to review that package

  • reply that mail, and say you want to review that
  • check if the package follows the policy
  • download the package on projects.openmoko.org
  • install that package to see if
    • installable?
    • executable able?
    • functions the claimed works actually works?
    • If it do something bad?
    • uninstall it and see if everything still ok?
  • if the package is okay, put the package in this file and the package will shown next day.

Review Policy

  • Packages in this repository shall not in OM repository
  • Program shall not collect user information and send to others unless it has very clear notification
  • Program shall not destroy the system
  • All packages shall be run-able on Neo
  • The package file name should refer which version of the project is compiled.