Gentoo Logo
Gentoo Spaceship

Note: Due to technical difficulties, the Archives are currently not up to date. GMANE provides an alternative service for most mailing lists.
c.f. bug 424647
List Archive: gentoo-dev
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
To: gentoo-dev@g.o
From: Dave Nellans <dnellans@...>
Subject: ebuild naming policy
Date: 15 Apr 2003 17:42:43 -0600
do we have an established naming policy for ebuilds, and where can i
find it?

my gripe is that when i submitted the ebuild for a program named "balsa"
(under app-sci/tbass) several devs told me i could not name it balsa
because the gnome email client balsa already uses that name.  i believed
that is why apps were listed under app-sci, dev-db, etc... which is why
this structure existed in the first place.  i was told however this was
not so and that this wasn't allowed.  in the end the ebuild was called
tbass which is very non-intuitive having a ebuild named something very
dissimilar to its common name.

all was fine untill i went to install ocaml and did emerge -s ocaml only
to find there are TWO packages named ocaml that co-exist seemingly
happily in different categories.  this brings back my original question
of if we have a specific naming policy or if some of the dev's are
mistaken about things.

if we don't have a naming policy yet, should we?  it seems as if naming
issues are becoming more significant now that the number of packages in
portage continues to grow.

any thoughts?
signature.asc (This is a digitally signed message part)
Re: ebuild naming policy
-- Chris PeBenito
Re: ebuild naming policy
-- Jon Portnoy
Lists: gentoo-dev: < Prev By Thread Next > < Prev By Date Next >
Previous by thread:
RE: Is there a process for marking ebuilds stable?
Next by thread:
Re: ebuild naming policy
Previous by date:
Re: Error
Next by date:
Re: ebuild naming policy

Updated Jun 17, 2009

Summary: Archive of the gentoo-dev mailing list.

Donate to support our development efforts.

Copyright 2001-2013 Gentoo Foundation, Inc. Questions, Comments? Contact us.