Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 03 Jun 2002 18:56:09 +0300
From:      Maxim Sobolev <sobomax@FreeBSD.org>
To:        .@babolo.ru
Cc:        julian@elischer.org, ports@FreeBSD.org
Subject:   Re: Splitting up ports.
Message-ID:  <3CFB9199.703C2210@FreeBSD.org>
References:  <200206030214.GAA09938@aaz.links.ru>

next in thread | previous in thread | raw e-mail | index | archive | help
"."@babolo.ru wrote:
> 
> 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).

The patch is incomplete, because it will generate invalid
PORTORIGIN's, thus breaking all tools that rely on in.

> Some of tools works with third levels ports as is: pkgdb, pib
> I do not use portbuild, pkg_install - do not try.

See above.

-Maxim

> 
> > 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




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3CFB9199.703C2210>