[gentoo-dev] Last rites: app-emacs/csharp-mode
# Ulrich Müller (5 Nov 2014) # Does not build with Emacs 24.4. # Last visible upstream activity in 2011. # Masked for removal in 30 days, bug #528374. app-emacs/csharp-mode pgp6x5SYzLxHT.pgp Description: PGP signature
Re: [gentoo-dev] Implicit system dependency
On Wed, Nov 5, 2014 at 12:30 PM, Luca Barbato wrote: > On 05/11/14 02:16, Michael Orlitzky wrote: >> >> When I was taking my ebuild quizzes, I asked for someone to clarify the >> implicit system dependency that we have enshrined in the devmanual: >> >>https://bugs.gentoo.org/show_bug.cgi?id=485356 >> >> There is... some agreement, but also special cases and special-special >> cases that are folklore-only at this point. To me it seems like a fine >> thing to ask the council to sort out, so I'm asking here for discussion. >> >> Can we come up with an idiot-proof list (or FLOWCHART, even!) of what >> should and should not be excluded from *DEPEND? >> > > Assume a C runtime and a C compiler do exist. > I would extend that to a C++ compiler and library as well.
Re: [gentoo-dev] Implicit system dependency
On 05/11/14 02:16, Michael Orlitzky wrote: When I was taking my ebuild quizzes, I asked for someone to clarify the implicit system dependency that we have enshrined in the devmanual: https://bugs.gentoo.org/show_bug.cgi?id=485356 There is... some agreement, but also special cases and special-special cases that are folklore-only at this point. To me it seems like a fine thing to ask the council to sort out, so I'm asking here for discussion. Can we come up with an idiot-proof list (or FLOWCHART, even!) of what should and should not be excluded from *DEPEND? Assume a C runtime and a C compiler do exist.
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in games-roguelike/stone-soup: stone-soup-0.14.1.ebuild stone-soup-0.15.1-r1.ebuild stone-soup-0.15.1.ebuild stone-soup-0.13.2.ebuild stone-soup
On Wed, 5 Nov 2014 17:34:06 +0100 Jeroen Roovers wrote: > On Wed, 5 Nov 2014 17:27:51 +0100 > Jeroen Roovers wrote: > > > On Wed, 05 Nov 2014 17:06:52 +0100 > > hasufell wrote: > > > > > Could you elaborate how to query that field via eix which is the > > > de-facto standard for finding packages? > > > > The official standard for finding packages is packages.gentoo.org. > > It (and the somewhat popular eix) have no problems at all reading > > the DESCRIPTION variable from the actual ebuilds. > > Which has me wondering if anything out there except human eyes every > reads . > > > jer > Porthole displays the long description when it exists and has always done so. -- Brian Dolbec
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in games-roguelike/stone-soup: stone-soup-0.14.1.ebuild stone-soup-0.15.1-r1.ebuild stone-soup-0.15.1.ebuild stone-soup-0.13.2.ebuild stone-soup
On Wed, 05 Nov 2014 17:36:34 +0100 hasufell wrote: > You were proposing that I strip down the DESCRIPTION field in my > ebuild and put the keywords relevant for finding the package into > in tag metadata.xml. No, I was proposing the overly long description should go to . As for the DESCRIPTION variable, it looks like it can be shortened easily. <<>>Dungeon Crawl Stone Soup - a roguelike RPG dungeon crawler Since it appears to be an actual roguelike (and not merely a game with permadeath as is how these days people interpret it) you could actually get it down to: "Dungeon Crawl Stone Soup - a dungeon crawler". > That leads to the question how do you read the longdescription field > from metadata.xml via eix or other commonly used tools for finding > packages. packages.gentoo.org doesn't allow it either. packages.g.o simply links to metadata.xml. I guess that works. jer
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in games-roguelike/stone-soup: stone-soup-0.14.1.ebuild stone-soup-0.15.1-r1.ebuild stone-soup-0.15.1.ebuild stone-soup-0.13.2.ebuild stone-soup
On 11/05/2014 05:27 PM, Jeroen Roovers wrote:
> On Wed, 05 Nov 2014 17:06:52 +0100
> hasufell wrote:
>
>> Could you elaborate how to query that field via eix which is the
>> de-facto standard for finding packages?
>
> The official standard for finding packages is packages.gentoo.org. It
> (and the somewhat popular eix) have no problems at all reading
> the DESCRIPTION variable from the actual ebuilds.
>
> # eix eix
> [I] app-portage/eix
> Available versions: 0.25.5 0.29.3{tbz2} ~0.29.6 ~0.30.0 ~0.30.1
> ~0.30.2 {clang debug +dep doc nls optimization security sqlite
> strong-optimization strong-security swap-remote tools
> zsh-completion LINGUAS="de ru"}
> Installed versions:
> 0.29.3{tbz2}(06:55:52 27/05/14)(dep doc nls sqlite -clang -debug
> -optimization -security -strong-optimization -strong-security
> -swap-remote -tools -zsh-completion LINGUAS="-de -ru")
>
> Homepage:http://eix.berlios.de
> Description: Search and query ebuilds, portage incl. local
> settings, ext. overlays, version changes, and more
>
> In this splendidly exemplary case, eix actually read the description
> from the ebuild - its very own metadata.xml does not have one.
>
>
I think you didn't get my question.
You were proposing that I strip down the DESCRIPTION field in my ebuild
and put the keywords relevant for finding the package into
in tag metadata.xml.
That leads to the question how do you read the longdescription field
from metadata.xml via eix or other commonly used tools for finding
packages. packages.gentoo.org doesn't allow it either.
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in games-roguelike/stone-soup: stone-soup-0.14.1.ebuild stone-soup-0.15.1-r1.ebuild stone-soup-0.15.1.ebuild stone-soup-0.13.2.ebuild stone-soup
On Wed, 5 Nov 2014 17:27:51 +0100 Jeroen Roovers wrote: > On Wed, 05 Nov 2014 17:06:52 +0100 > hasufell wrote: > > > Could you elaborate how to query that field via eix which is the > > de-facto standard for finding packages? > > The official standard for finding packages is packages.gentoo.org. It > (and the somewhat popular eix) have no problems at all reading > the DESCRIPTION variable from the actual ebuilds. Which has me wondering if anything out there except human eyes every reads . jer
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in games-roguelike/stone-soup: stone-soup-0.14.1.ebuild stone-soup-0.15.1-r1.ebuild stone-soup-0.15.1.ebuild stone-soup-0.13.2.ebuild stone-soup
On Wed, 05 Nov 2014 17:06:52 +0100
hasufell wrote:
> Could you elaborate how to query that field via eix which is the
> de-facto standard for finding packages?
The official standard for finding packages is packages.gentoo.org. It
(and the somewhat popular eix) have no problems at all reading
the DESCRIPTION variable from the actual ebuilds.
# eix eix
[I] app-portage/eix
Available versions: 0.25.5 0.29.3{tbz2} ~0.29.6 ~0.30.0 ~0.30.1
~0.30.2 {clang debug +dep doc nls optimization security sqlite
strong-optimization strong-security swap-remote tools
zsh-completion LINGUAS="de ru"}
Installed versions:
0.29.3{tbz2}(06:55:52 27/05/14)(dep doc nls sqlite -clang -debug
-optimization -security -strong-optimization -strong-security
-swap-remote -tools -zsh-completion LINGUAS="-de -ru")
Homepage:http://eix.berlios.de
Description: Search and query ebuilds, portage incl. local
settings, ext. overlays, version changes, and more
In this splendidly exemplary case, eix actually read the description
from the ebuild - its very own metadata.xml does not have one.
jer
Re: [gentoo-dev] Re: [gentoo-commits] gentoo-x86 commit in games-roguelike/stone-soup: stone-soup-0.14.1.ebuild stone-soup-0.15.1-r1.ebuild stone-soup-0.15.1.ebuild stone-soup-0.13.2.ebuild stone-soup
On 10/28/2014 01:17 AM, Jeroen Roovers wrote: > On Mon, 27 Oct 2014 19:58:15 + > hasufell wrote: > >> I want to keep the over-long description unless we have some sort of >> ebuild aliases. > > > Could you elaborate how to query that field via eix which is the de-facto standard for finding packages?
