[Fribidi-discuss] Compiled on OS X; how to publish the binary?

[Tzafrir Cohen]

On Tue, Apr 15, 2003 at 09:29:20AM +0300, Nir Soffer wrote:
> I compiled fribidi (with the help of Behdad) and used it successfully.
> 
> How can I publish the binary? the fribidi file is only a script behind 
> the library. When I installed it, using make install, I so it copied 
> many files to various directories.

What binary? For who?

The fribidi library for others to build programs against, or the
command-line filter fribidi?

> 
> In OS X, its very easy to create a user friendly installer - but I need 
> to know what are the files that are needed and where each one should be 
> installed. Where is that information?

It is nice to be able to install a package. But what about upgrading a
package?

I keep hearing here that the next version of the interface is planned.
Therefore we have once again a major version of the library, that breaks
binary compatibility (atleast forward compatibility).

> 
> It seems that all this could be much easier if the project was better 
> organized. For example, what about this layout:
> 
> fribidi-versionnumber // root folder
> 	src // c files
> 	headers // h files
> 	config // file releated to the configure stage	
> 	make // file that releated to the make stage
> 	install // contain all the file that get installed when you do make 
> install,
> 			with an install script.
> 	unidata // already exists
> 	charsets // with all the charset files

What does it matter? Why don't you use 'make install' and tweak it to
your needs?

When packaging an RPM package one generally runs (in the %install phase)
a "make install" with a PREFIX (or "prefix", or whatever) of some
temporary directory. Thus you can easily get only the files installed by
"make install".

-- 
Tzafrir Cohen                       +---------------------------+
http://www.technion.ac.il/~tzafrir/ |vim is a mutt's best friend|
mailto:tzafrir at technion.ac.il       +---------------------------+