I figured I'd let everyone know that this weekend sometime I plan on
changing the cairo ebuilds to have IUSE="+svg". It seems like a lot of
default installs of various things out of the box actually rely on
cairo to have SVG support and users are presented with an ugly error
message out of the box
On Thu, Feb 4, 2010 at 7:05 PM, Mike Frysinger wrote:
> On Thursday 04 February 2010 16:37:01 Tiziano Müller wrote:
>> While some people already discovered the upstream metadata tags, there
>> are only 8 ebuilds using them so far. Mostly I am to blame for that,
>> since I forgot to send out a prop
Am Freitag, den 05.02.2010, 11:34 +0100 schrieb Alexis Ballier:
> > Other sites I'd like to add:
> > - pypi
> > - google-code
> > - ctan ... if someone can identify a key for packages
>
> I don't know what you exactly mean by a key, but for ctan the
> catalogue [1,2] may be what you're looking for
Am Freitag, den 05.02.2010, 20:16 +0300 schrieb Peter Volkov:
> В Чтв, 04/02/2010 в 22:37 +0100, Tiziano Müller пишет:
> > The upstream tags are meant as a way to track information about
> > - id of a hosting or indexing site (automated version bump checks)
>
> Does there exist any scripts for thi
В Чтв, 04/02/2010 в 22:37 +0100, Tiziano Müller пишет:
> The upstream tags are meant as a way to track information about
> - id of a hosting or indexing site (automated version bump checks)
Does there exist any scripts for this?
--
Peter.
It is planned that ebuilds of Python 3.2 will automatically set Python 3.2 as
main active
version of Python. (Currently ebuilds of Python 3.1 do not automatically set
Python 3.1
as main active version of Python.) Final release of Python 3.2 is currently
scheduled on
2010-12-11, so you have over
> Other sites I'd like to add:
> - pypi
> - google-code
> - ctan ... if someone can identify a key for packages
I don't know what you exactly mean by a key, but for ctan the
catalogue [1,2] may be what you're looking for.
If I understood correctly, a key would be $PN and the relevant
information f
