From owner-freebsd-ports Sun Jun 2 19:14:28 2002 Delivered-To: freebsd-ports@freebsd.org Received: from aaz.links.ru (aaz.links.ru [193.125.152.37]) by hub.freebsd.org (Postfix) with ESMTP id 4C82E37B400; Sun, 2 Jun 2002 19:14:22 -0700 (PDT) Received: (from babolo@localhost) by aaz.links.ru (8.9.3/8.9.3) id GAA09938; Mon, 3 Jun 2002 06:14:56 +0400 (MSD) Message-Id: <200206030214.GAA09938@aaz.links.ru> Subject: Re: Splitting up ports. In-Reply-To: <200206021030.g52AURZ72904@vega.vega.com> from "Maxim Sobolev" at "Jun 2, 2 01:30:27 pm" To: sobomax@FreeBSD.org (Maxim Sobolev) Date: Mon, 3 Jun 2002 06:14:56 +0400 (MSD) Cc: julian@elischer.org, ports@FreeBSD.org From: "."@babolo.ru MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-ports@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org Maxim Sobolev writes: > Unfortunately it isn't as easy as it sounds. There are many places where Yes, I understand. But ... > 2-level structure (category/portname) is assumed (for example: pkg_install, > portupgrade, portbuild, bsd.port.mk, ports www pages etc), therefore unless ... bsd.port.mk is easy - see PR 38593 (oh, sorry - distfiles was not up to day - repaired). Some of tools works with third levels ports as is: pkgdb, pib I do not use portbuild, pkg_install - do not try. > someone is willing to find and fix all those places there will be no move > forward. So far I do not see somebody willing and capable of doing that. > > -Maxim > > > > > > Julian Elischer writes: > > > The time has come to start working on making a hierachy from teh > > > ports tree.. > > > there are just too many ports now! > > > > > > I was thinking of the following kinds of taxonomic scheme: > > > > > > first order... basic current scheme (though > > > possibly 'national' types should be handled differntly) > > > > > > second order: dependent on class but for example: > > > audio/midi and audio/libraries audio/players... etc > > > it really depends on the major class what the subclasses would be. > > > > > > also, net/analysis net/benchmarks net/dns net/transfer net/security > > > > > > etc. > > > > > > it's getting a bit crouded in there! > > And another end :-) of tree: > > I propose to group dependant ports > > in one ports directory to base port, for example: > > ports/x11-wm/sapphire/sapphire > > ports/x11-wm/sapphire/sapphire-themes > > ports/x11-wm/sapphire/sapphire-another-themes > > (no sapphire-another-themes in ports now) > > See ports/38593 Three level ports: Patch and new ports > > as another example with some patch. > > > > Alternative to proposed path is to enlage list > > of valid categories in such a way: > > VALID_CATEGORIES+= audio/midi audio/libraries ... so on. > > But a list of categories become so > > flexible (x11-wm/sapphire is a category > > in above) so some of ports submits > > will change of VALID_CATEGORIES in Mk/bsd.port.mk. > > > > Just remove VALID_CATEGORIES check? > > Separate list of VALID_CATEGORIES to different file? > > different files in main (first level) category directories? > > Do not check subcategories (as PR/38593)? > > > > Sorry for bad English > > > > -- > > @BABOLO http://links.ru/ > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > > with "unsubscribe freebsd-ports" in the body of the message > > > > > > -- @BABOLO http://links.ru/ To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ports" in the body of the message