Date: Sun, 18 Feb 2001 22:12:10 -0700 From: Wes Peters <wes@softweyr.com> To: Terry Lambert <tlambert@primenet.com> Cc: Mark Murray <mark@grondar.za>, Jordan Hubbard <jkh@winston.osd.bsdi.com>, arch@FreeBSD.ORG Subject: Re: Moving Things [was Re: List of things to move from main tree] Message-ID: <3A90AB2A.E2C4F64@softweyr.com> References: <200102190406.VAA11061@usr05.primenet.com>
next in thread | previous in thread | raw e-mail | index | archive | help
Terry Lambert wrote:
>
> > Right. Personally, i like XML, but the XML support stuff is big,
> > and that scares me.
>
> The Xerces source code is 5 1/2 MB, compressed. I don't know how
> big the Gnome library is, or how big the Xerces shared library is,
> once it's compiled.
>
> If XML is going to be used during install, maybe it'd be a good
> idea to build a small LALR parser, which only knows about the
> grammar to be used for the specific application.
Expat helps build such parsers. The syntax is slightly weird, but it's
a lot smaller than 5.5 MB.
> I think that whatever gets done, people have to accept that there
> are some basic constraints on some of this stuff, having to do
> with the source repository layout.
>
> For example, I think it would be a bad idea to move the games
> around in the repository, just because people want them to be
> ports, instead of installed by default. It makes no sense to do
> that.
I think the idea is push everything that cannot be considered a core
part of the operating system into a different part of the tree, that
can be chosen from ala carte. This is a lot more extensive than
moving games to the ports tree. Telnet, ftp, rtools, UUCP, sendmail,
DNS, etc.
> I also think that a nice first run at lists of files installed
> would be a good thing; frankly, it's very hard to relocate most
> net software, to know where and what was installed, and to then
> build something that expects to be installed in a particular
> location, make an image, and then do the install later. Shared
> libraries are a particular problem, in that regard.
The package dependency mechansim helps take care of that. If you
select a package that requires a shared library you don't have, the
dependency will install the shared library package as well.
> The best way I've thought of to address that so far is to hack
> make to log calls to "install", "mv", and "cp", when their
> target isn't interior to the build hierarchy. The utility being
> built would be logged, along with what got installed as part of
> the build. Not perfect, but then you at least know what files
> ended up where as a result of a "make install" for any given
> utility.
>
> Thinking more on this, I think that make should probably scream
> about the use of "mv" and "cp" instead of "install", so that they
> can be replaced with "install". Then you could log with install
> along, just by adding an option that let you add the name of the
> thing to the log file, as another argument.
In that case, we should add an option to install to perform links and
symlinks, and have make scream about "ln" as well.
--
"Where am I, and what am I doing in this handbasket?"
Wes Peters Softweyr LLC
wes@softweyr.com http://softweyr.com/
To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-arch" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3A90AB2A.E2C4F64>