Added by Thilo Pfennig, last edited by Thilo Pfennig on Mar 31, 2007

Labels:

deleteme deleteme Delete
Enter labels to add to this page:
Wait Image 
Looking for a label? Just start typing.

This page contains some basic tips and rules to submit a package to Foresight. Please feel free to change this page radically. Just wanted to start this of

Decide where it should go

There are two repositories now.

  • foresight.rpath.org@fl:1-devel - The development repository for the stable @fl:1 repository. This pages will be burned on DVD and from these packages I added to the group 'group-dist' of fl:1. So not all packages will be distributed. The packages here are shadowed to fl:1 if a core developer who can do it thinks its worth. These packages are the ones we think every user should have.
  • foresight.rpath.org@fl:1-contrib - This is a repository where now every package will gbe available for all users. The packages here are generally not considered of use for general users and cant be counted as essential to a GNOME core distribution.

How to submit a package

  • Please make yourself an account on Rpath and request to be developed as developer for http://foresight.rpath.org/
  • If you have managed to make a package you should test its general functionality before submitting source and/or binary.
  • If you are not sure how to do things please ask in #foresight or the foresight-devel mailing list.

Open Questions ?

  • Do we want to force alphabetical sorting of buildRequires?
    • I vote gainst because this would mean that we would see a lot of changes and submissions that do not contain fixes. I rather like new buildRequires to be in one line at the end. – Thilo Pfennig