Re: [Scrollkeeper-devel] ScrollKeeper-0.1 Proposal #3

[Will A. <wi...@ph...>]

On Mon, Nov 13, 2000 at 09:48:25AM +0000, Nik Clayton wrote:
> > The OMF documents are manipulated during the application
> > build process, generally as part of 'make all'.  The purpose of this
> > is to (1) substitute the correct URL of the document where it will
> > actually be installed, which is not generally known until build time,
> > and to (2) extract the OMF from DocBook documents into a seperate file.
> > (NOTE: #2 may not be supported in ScrollKeeper 0.1)
> 
> You probably don't know where the application is going to be installed until
> install time, not build time.  Using the FreeBSD ports tree, it's trivial
> to do
> 
>     cd /usr/ports/foo/bar
>     make
>     make PREFIX=/somewhere/else install
> 
> Similarly, if you're building packages on BSD (or RPMs, or whatever) the
> end user can change the install path after the package has been built, but
> before it has been installed.

On a similar topic..

Personally, I've always hoped that the ScrollKeeper protocol required a
package listing.  This would reduce turnaround time in creating FreeBSD
ports, but probably has the drawback of being difficult to maintain for
the application vendor, if there are a large number of files.

However, it would be a nice thing.. I don't know what they use for debs,
rpms and such, but PLISTs are currently the biggest pain in the ass for
ports maintenance.

Nik, I probably should have talked to you about this at BSDCon... sorry
it didn't cross my mind at the aqarium.  :-(

-- 
wca