Community Repository
From MEPIS Documentation Wiki
Contents |
Introduction
This is a package repository run by and for the Mepis Community. This page contains instruction on how to set up access to the repository in your sources list, how to request packages, and how to assist the community by testing.
Disclaimer - Please Read
We (the Packaging Team) have attempted to make the contents of the repo as stable & troublefree as possible for you - but there are no guarantees. We are following strict packaging guidelines to try and ensure no computability issues - however if you do use the repo, you acknowledge that you do this at your own risk. I (Brooko) am using it on my production machine - so this should give you my opinion regarding compatibility / stability.
Using The Repository
To make use of the repository add the following to your sources list (found at /etc/atp/sources.list):
deb http://mepis.blue-pearls.net/repo/ mepis7cr main non-free
Or a simpler method is to open Synaptic, and add a repository using the same fields.
Base Procedures
- Community members will use the ML Package Request thread to request packages.
- Upon request of a package, a Community Packaging Team member will either volunteer to build it (confirm in same post), or if thread unanswered for a period of 7 days (unlikely) then the Community Packaging Project Leader will assign the request to a "Packaging Pod". The package builder (once assigned) should post in the package request thread to advise that the requested package has been assigned.
- The package builder then posts in the Package List Community Repository Package List - listing the full package details, and builder/maintainer. This is done so that we don't have two people assigned to the same package.
- The packager then builds the requested package using the Mepis Package Building Guide.
- Once package has been built, the builder starts a new thread on Mepis Lovers in the News/Package Status forum. In the thread list - the package, any known dependency issues, give a link to a downloadable deb file, and request testing and feedback.
- After package has been confirmed to be working with no issues, package builder emails zipped file to his pod maintainer. Zip file to contain the deb(s), dsc, diff and source files.
- Maintainer checks files for virus, uploads them to the community repository, checks that they are accessible, and then posts in the same News/Package Status forum thread to confirm completed packages have been uploaded.
Pods / Structure
- The Mepis Packaging Team is divided into several (at the moment 3) sub-teams or pods. Each pods consists of a Maintainer and 2-3 package builders.
- Only Maintainers can upload packages to the Community Repository
- Maintainers can not upload their own packages. Maintainers - who are also builders - can also be building members in a different Maintainer's pod.
- If for any reason a Mepis Packaging Team member is unable to continue with their role, it is very important that they try and find a replacement within the community - and organise seamless continuity.
- If you are intersted in joining the Mepis Packaging Team - please get in touch with a team member - list at Introduction to the Team thread on Mepis Lovers.
Packages
- How can I find out which packages are in the Community Repository?
- All packages are tracked on this page
- What packages will be in the Community Repository?
- Any packages requested by the community which we are able to build.
- Anything that isn't found in Etch, or is far out of date with Etch versions are requested.
- Will the source code be provided?
- We ask that all package contributers adhere to the license of the program. As part of our procedures, we've indicated for source to be provided by the builders, and the intention is to make this available in our Community Repository.
- How many versions do I need to maintain?
- We would like to keep packages synced for both 64bit and 32bit versions of Mepis 7 Series. We are aware that special cases arrive where only one build is available, so this is not an absolute rule.
