Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 567062 - media-libs/fontconfig-ultimate-9999: version bump
Summary: media-libs/fontconfig-ultimate-9999: version bump
Status: RESOLVED OBSOLETE
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal enhancement (vote)
Assignee: Gentoo Fonts Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-11-29 02:00 UTC by cristiano04
Modified: 2023-05-10 12:56 UTC (History)
4 users (show)

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


Attachments
fontconfig-ultimate-9999.ebuild (fontconfig-ultimate-9999.ebuild,3.53 KB, text/plain)
2015-11-29 02:01 UTC, cristiano04
Details
fontconfig-ultimate-9999.ebuild (fontconfig-ultimate-9999.ebuild,3.86 KB, text/plain)
2015-11-29 02:39 UTC, cristiano04
Details
fontconfig-ultimate-9999.ebuild (fontconfig-ultimate-9999.ebuild,3.65 KB, text/plain)
2015-11-29 02:56 UTC, cristiano04
Details
Empty KEYWORDS (fontconfig-ultimate-9999.ebuild,3.64 KB, text/plain)
2015-11-30 17:52 UTC, cristiano04
Details

Note You need to log in before you can comment on or make changes to this bug.
Description cristiano04 2015-11-29 02:00:31 UTC
9999.ebuild.
Has been requested quite a few times, and so, here it is.

Reproducible: Always
Comment 1 cristiano04 2015-11-29 02:01:02 UTC
Created attachment 418094 [details]
fontconfig-ultimate-9999.ebuild
Comment 2 cristiano04 2015-11-29 02:39:51 UTC
Created attachment 418098 [details]
fontconfig-ultimate-9999.ebuild

Oops, fixes noto,adds heuristica, and updates the new infinality_ft style nomenclature. 
Also adds proper warnings.

https://bohoomil.com/doc/05-fonts/
Comment 3 cristiano04 2015-11-29 02:56:42 UTC
Created attachment 418100 [details]
fontconfig-ultimate-9999.ebuild

Introduced a minor bug that's been done away with and removed legacy code. Tested the package, it works as intended.
Comment 4 Brian Evans (RETIRED) gentoo-dev 2015-11-30 17:47:52 UTC
(In reply to cristiano04 from comment #3)
> Created attachment 418100 [details]
> fontconfig-ultimate-9999.ebuild
> 
> Introduced a minor bug that's been done away with and removed legacy code.
> Tested the package, it works as intended.

FYI, from VCS packages must have empty KEYWORDS
Comment 5 cristiano04 2015-11-30 17:52:20 UTC
Created attachment 418212 [details]
Empty KEYWORDS

(In reply to Brian Evans from comment #4)
> (In reply to cristiano04 from comment #3)
> > Created attachment 418100 [details]
> > fontconfig-ultimate-9999.ebuild
> > 
> > Introduced a minor bug that's been done away with and removed legacy code.
> > Tested the package, it works as intended.
> 
> FYI, from VCS packages must have empty KEYWORDS

Thanks for the information. Fixed it.
Comment 6 Witold Piłat 2015-11-30 18:24:16 UTC
Where was it requested? As a proxy maintainer I would like to know if there is a discussion on this ebuild going somewhere :-)

There was a live ebuild back in the sunrise, but I considered it impractical for these reasons:

1. Upstream's development pace
2. Fragility to any changes in the source package.
3. I'm not a gentoo dev so I'm unable to keep pushing fixes all the time.

If I was involved in fontconfig-ultimate development and needed a live ebuild I'd consider keeping it in an overlay where I've got push access.
Just my opinion.
Comment 7 cristiano04 2015-11-30 18:43:29 UTC
(In reply to Witold Piłat from comment #6)
> Where was it requested? As a proxy maintainer I would like to know if there
> is a discussion on this ebuild going somewhere :-)
> 
> There was a live ebuild back in the sunrise, but I considered it impractical
> for these reasons:
> 
> 1. Upstream's development pace
> 2. Fragility to any changes in the source package.
> 3. I'm not a gentoo dev so I'm unable to keep pushing fixes all the time.
> 
> If I was involved in fontconfig-ultimate development and needed a live
> ebuild I'd consider keeping it in an overlay where I've got push access.
> Just my opinion.

Well, there are quite some forums out there,  and then there are imageboards. 

You are right, and recently there's been one such case where bohoomil broke something (not exporting INFINALITY_FT_FILTER_PARAMS), but it was fixed within minutes. The infinality_style attribute was also changed (styles are no longer 1-5, they are ultimate{1,5}), but that is precisely why the live ebuild should use the default values (ultimate3).

If you're concerned about new fonts being added, we could lessen the burden by... putting it on the infinality-ultimate-meta maintainers as opposed to listing every font package manually. :^]

Besides, I think people are aware of the risks 9999 ebuilds entail. :]
Comment 8 Ian Delaney (RETIRED) gentoo-dev 2015-12-09 09:19:58 UTC
(In reply to Witold Piłat from comment #6)
> Where was it requested? As a proxy maintainer I would like to know if there
> is a discussion on this ebuild going somewhere :-)
> 
> There was a live ebuild back in the sunrise, but I considered it impractical
> for these reasons:
> 
> 1. Upstream's development pace
> 2. Fragility to any changes in the source package.
> 3. I'm not a gentoo dev so I'm unable to keep pushing fixes all the time.
> 
> If I was involved in fontconfig-ultimate development and needed a live
> ebuild I'd consider keeping it in an overlay where I've got push access.
> Just my opinion.

As the designated proxy you ought to have been involved at the outset, and you were by being CC'd. As designated maintainer you are automatically involved, and you already have authority re where this goes. To my view, since you have in fact entered reply here, this ebuild requires both your consent and cross testing before it proceeds. Personally I don't favour live ebuilds unless there's some flurry of active development or extenuating cause.

Sunrise is am option, but one I gather is somewhat inactive in recent history. You have right to say I wish not to pursue with this live option.

As a proxy maintainer you can keep pushing fixes at the pace and level of your choice.