Alan Coopersmith wrote:
> Laszlo (Laca) Peter wrote:
>> Which leads us to the packaging bits: prototype_com, prototype_sparc,
>> prototype_i386: these could really be generated.  It's really easy to
>> make mistakes when writing these manually.  
> 

> It's also really easy for build problems to cause files not to be built,
> and then autogenerated package maps would simply be missing files.   The
> autogeneration of packaging info has always seemed to me to be one of the
> worst misfeatures of the JDS build system, and I'm sure you remember even
> more bugs than I do of files simply disappearing or reappearing in builds
> because of it.
> 

> I much prefer having the static package maps checked into the tree, so that
> if a file is not built, the package build fails and it's noticed and fixed
> immediately.   Sure - have tools to build those, but require human 
> intervention
> to change the contents of the package so that anyone who builds it can be
> sure they've gotten the exact same set of files as the official builds,
> including the future official builds.
> 

I don't think the JDS build system forces you to do that.

When I used to use it, I hardly ever used wildcard expansion in spec 
file file lists, but enumerated files individually. IIRC that gave you 
notification both ways: if the spec file attempted to pack a file that 
was gone, packaging failed. If a file installed into DESTDIR by make 
install was not packaged, then packaging also failed and complained[*]. 
So there you automatically get informed about package map changes and 
you then have to decide whether to add the extra files to the files 
section or to explicitly omit them, by removing them in your install 
section. Unless the needed changes are more complicated and require 
patching the upstream sources, you only have to edit a single file for 
this (per package).

- J?rg

[*] This is where I'm not entirely sure that I recall correctly. Most of 
what I built with this system, was built on Linux as well as Solaris. 
I'm not sure from memory whether Solaris pkgbuild also mimicks this 
complaint from rpmbuild.

-- 
Joerg Barfurth           phone: +49 40 23646662 / x66662
Software Engineer        mailto:joerg.barfurth at sun.com
Desktop Technology       http://reserv.ireland/twiki/bin/view/Argus/
Thin Client Software     http://www.sun.com/software/sunray/
Sun Microsystems GmbH    http://www.sun.com/software/javadesktopsystem/



Reply via email to