Go to:
Gentoo Home
Documentation
Forums
Lists
Bugs
Planet
Store
Wiki
Get Gentoo!
Gentoo's Bugzilla – Attachment 1134 Details for
Bug 1523
[IDEA] Offload work by distributing trivial ebuild maintenance to users, introduce a simple stability voting system and have a core team approve them to the Portage tree.
Home
|
New
–
[Ex]
|
Browse
|
Search
|
Privacy Policy
|
[?]
|
Reports
|
Requests
|
Help
|
New Account
|
Log In
[x]
|
Forgot Password
Login:
[x]
sample Status file (update)
Status.skel (text/plain), 1.89 KB, created by
George Shapovalov (RETIRED)
on 2002-05-25 05:13:43 UTC
(
hide
)
Description:
sample Status file (update)
Filename:
MIME Type:
Creator:
George Shapovalov (RETIRED)
Created:
2002-05-25 05:13:43 UTC
Size:
1.89 KB
patch
obsolete
>#This file is intended to be used for keeping trace of ebuild states/stability levels >#In comparision to mangling ebuild name this seems to be >#easier to implement, more flexible, more extensibe (well, you got it :)) >#way of doing things > >#So the way this is supposed to work: >#This file lists all confirmations, approvals and other changes to ebuild status >#for every ebuild in the dir (one per line) ># >#file format: >#ebuild-name confirmed_flag approved_flag > >#boolean switches like confirmed, approved take yes/no/core/unstable >#with core>yes>no>unstable > >#for example gpc-2.1.ebuild having approved status will have: >2.1 yes yes >#and gpc-2002533.ebuild (apparently fake date) with new status will have: >2002433 no no > >#function: >#ebuild not listed in this file automatically gets "no" to all entries >#thus effectively getting "new" status ># >#core in any position marks package as "core" >#nominally core should be present in approved column > >#"unstable" in any position marks ebuild as unstable >#old masking functionality is maintained. > >#It is possible to differentiate conf. and appr. columns, so that >#unstable in "approved" position will mask an ebuild >#this can be used as an alternative to listing ebuild in package.mask > >#These ebuild states are used in conjunction with the following flags >#(defined in make.conf, overriden in command line) >#STABILITY_LEVEL={approved(yes,yes),approved_unconfirmed(no,yes), ># confirmed(yes,no),all(no,no)} >#RSYNC_LEVEL={same as above, with "all" fetching unstable packages} >#parameters in brakets define minimum level at which ebuild is considered with >#such ordering: core>yes>no>unstabe >#thus core packages are visible always as well as approved ones >#while confirmed(yes,no) only at StabilityLevel="confirmed" >#note that even STABILITY_LEVEL="all" will ignore unstabble packages. >#This is by design, to prevent especially unrestfull users from breaking their systems :)
You cannot view the attachment while viewing its details because your browser does not support IFRAMEs.
View the attachment on a separate page
.
View Attachment As Raw
Actions:
View
Attachments on
bug 1523
:
1086
|
1087
|
1088
| 1134