Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 742413 - dev-scheme/chicken-5.2.0: version bump (ebuild included)
Summary: dev-scheme/chicken-5.2.0: version bump (ebuild included)
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Scheme Project
Keywords: EBUILD
Depends on:
Reported: 2020-09-14 04:49 UTC by Christopher Bayliss
Modified: 2021-01-17 09:40 UTC (History)
2 users (show)

See Also:
Package list:
Runtime testing required: ---

chicken-5.2.0.ebuild (chicken-5.2.0.ebuild,1.61 KB, text/plain)
2020-09-14 04:49 UTC, Christopher Bayliss
chicken-5.2.0.ebuild-unified.diff (chicken-5.2.0.ebuild-unified.diff,1.50 KB, text/plain)
2020-09-14 06:38 UTC, Christopher Bayliss

Note You need to log in before you can comment on or make changes to this bug.
Description Christopher Bayliss 2020-09-14 04:49:02 UTC
Created attachment 660063 [details]


Please find attached chicken-5.2.0.ebuild

This is my first time submitting an ebuild, apologies if I'm not following established protocol to the letter.

While based on the chicken-4.13.0-r1.ebuild, here is a list of all the differences:

 * updated to EAPI 7

 * no longer use versionator, instead use ${PV}

 * all keywords changed to unstable

 * added a space after '#' on lines 21 and 22 for [subjectively] easier reading of the comment

 * rm 'manual-html' instead of 'manual', otherwise the 'doc' useflag does nothing

 * modules in 5.2 are found in '11' not '8'

Comment 1 Sam James archtester gentoo-dev Security 2020-09-14 05:58:24 UTC

Some notes:
* Provide a unified diff to make review easier (diff -u chicken-4.13.0-r1.ebuild chicken-5.2.0.ebuild)

* Provide the GCO sign off, either in a comment, or at the top of the attachmentt (see:

*  Bugzilla vs mail vs Github vs ??? as preferred methods are a bit of an inconsistency between maintainers.

Personally, I find Github easier to review user contributions, but I'm not the maintainer here. 

If you don't hear anything back after a while (about 3-4 weeks is the norm for "maintainer timeout"), you could post a pull request there and/or email the maintainers to give them another opportunity to respond.
Comment 2 Christopher Bayliss 2020-09-14 06:38:08 UTC
Created attachment 660096 [details]
Comment 3 Christopher Bayliss 2020-09-14 06:38:53 UTC
Signed-off-by: Christopher Bayliss <>