Date: Wed, 27 Nov 2002 15:04:35 -0500 From: parv <parv_fm@emailgroups.net> To: f-ports <freebsd-ports@FreeBSD.ORG> Subject: Re: creating ports INDEX from actual installed ports Message-ID: <20021127200435.GB21971@moo.holy.cow> In-Reply-To: <5.2.0.9.2.20021126205857.00a7da30@pozo.com> References: <20021127045833.GA17350@moo.holy.cow> <5.2.0.9.2.20021126205857.00a7da30@pozo.com>
next in thread | previous in thread | raw e-mail | index | archive | help
in message <5.2.0.9.2.20021126205857.00a7da30@pozo.com>,
wrote Manfred Antar thusly...
>
> At 11:58 PM 11/26/2002 -0500, parv wrote:
> >before i start (in perl) ... does anybody aware of past or present
> >efforts to generate ports INDEX from _installed_ports_ (independent
> >of $PORTSDIR/Tools/make_index)?
> >
> >
> >i checked portupgrade-20021113, it uses above perl program; nothing
> >else seemed to standout in ports/sysutils.
>
> portsdb -u -U works
i should have asked for independence from the "describe" target
(instead of make_index). anyway...
portupgrade comes close, but not quite. while making INDEX(|.db)
via portsdb, it generated following error (wrapped for e-mail) among
others...
"/usr3/ports/x11-toolkits/ruby-gtk/Makefile", line 25: Could not find \
/usr3/ports/x11-toolkits/ruby-gtk/../../x11/ruby-gnome/Makefile.common: \
malformed entry: "/usr3/ports/x11-toolkits/ruby-gtk/Makefile", \
line 25: Could not find /usr3/ports/x11-toolkits/ruby-gtk/../../x11/ruby-gnome/Makefile.common
make: fatal errors encountered -- cannot continue: malformed entry: \
make: fatal errors encountered -- cannot continue
*** Error code 1: malformed entry: *** Error code 1
`all' not remade because of errors.: malformed entry: `all' not remade because of errors.
make_index: no entry for: /usr2/local
make_index: no entry for: /usr2/local
make_index: no entry for: /usr/ports/x11-toolkits/ruby-gtk
...despite the errors, both indexes were made correctly. that's
much more than that can be said about ports own index making.
re-reading various portupgrade supporting programs/modules/libs, it
does give me some idea where to start... most importantly to skip
using make, just parse the damn Makefile where- & whenever possible.
i think where "describe" target fails (in case of missing
directories) & make usage might be important is in deducing the
dependencies.
- parv
--
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?20021127200435.GB21971>