Am 11.09.2004 um 00:38 schrieb Daniel Macks:
On Fri, Sep 10, 2004 at 10:43:06AM +0200, Jan Paul Schmidt wrote:
I started to do a package info for streamdvd. The info file is attached.
In general, better to use the Package Submissions tracker on Fink's SourceForge website. That way we don't have to keep slinging files through email.
The attachment was meant to let people see what I did. Not to include it in fink. Maybe it was not clear, that I'm not done with packaging.
First question
Is the attached info file the right way to do it? It works here, but as
it is my first package for fink and I'm not familiar with it, I'm not
sure with for example the CompileScript key and the use of enviroment
variables.
Looks like a good start. Packages that follow some standards automatically use CPPFLAGS and LDFLAGS, and fink makes it easy to set these (see the 'SetENVVAR' entry in the Fields section of the Packaging Manual for all the standard vars). But some packages aren't so standard. Basically you just do whatever it takes to get the thing compiled:)
That's what I did ;o) One reason to ask was there is no mention of CPATH and LIBRARY_PATH in the packaging manual. As I'm quite lazy about patch files I used them. I'm also a bit surprised, fink don't use them itself, as it is a easy way to add include und library paths. But there are probably reasons beyond my knowledge.
Second question
Fink always looks for the source at the mirrors first. In case of a new
package, this is quite anoying, as it fails. Is there a way around
this?
Fink always looks wherever you have told it to look based on the MirrorOrder entry in /sw/etc/fink.conf. Running 'fink configure' is an easy way to change this setting.
That's true, but streamdvd is currently only available from the authors homepage and I did not found a setting to say, download from the authors homepage first and don't use Fink, SourceForge, GNU whatever if not specified.
Third question
Is it the task of a package maintainer to do cosmetic corrections for compiling? streamdvd for example spits out some warnings about assignments etc.
As long as it runs, I don't usually worry too much about many compiler warnings. OTOH, some I do recognize as being due to different headers on OS X vs. linux; if it's easy to fix, I fix it.
Sounds like I would do it ;o)
Fourth question
I get linker warnings like
ld: warning prebinding not disabled because (__PAGEZERO segment
(address = 0x0 size = 0x1000) of streamdvd overlaps with __TEXT segment
(address = 0x0 size = 0x15000) of /sw/lib/libdvdread.3.dylib
Never saw this stuff under Linux up till now. What does it mean? Is there something to take in account when linking under fink?
Prebinding something that can be done to binaries to make them load faster at run-time. I'm pretty sure linux does not do prebinding.
There is something which is called prelinking on Linux. But I'm not familiar with either. Is there a short introduction to prebinding?
Fink has a clever hack to make it easy to get everything prebound correctly, but has a side effect of temporarily putting things in overlapping locations. Later, they are shifted later so that they no longer overlap, but ld has no way of knowing we're that smart; you can ignore this warning.
OK, altough these warnings look really heavy sometimes.
jps
-------------------------------------------------------
This SF.Net email is sponsored by: YOU BE THE JUDGE. Be one of 170
Project Admins to receive an Apple iPod Mini FREE for your judgement on
who ports your project to Linux PPC the best. Sponsored by IBM. Deadline: Sept. 13. Go here: http://sf.net/ppc_contest.php
_______________________________________________
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel
