[nycbug-talk] Make package-recursive problem

[Marc Spitzer]

Matt,

It s not a bug with the ports system.  It is doing what it should do:

I am the nagios port and I am building nagios:
1: I need/depend on apache
2: apache is not installed on the system
3: I tell the apache port to build
...
N: nagios is built/installed/packaged
N+1: have a beer yea

That is the default behavior of ports, and it is doing the right thing
by installing what it was told by the port maintainer it needed
installed as a precondition to build/install/package-up

Now my memory is a bit fuzzy here, but I think you can tell ports to
attempt to use a binary packages first, then build.  the thing is you
need to setup your own package repository to make this work, it may be
as simple as seting a var to point to /usr/ports/packages.

Now there is another problem with ports, well port maintainers
actually, such that ports will not build a package that will install
correctly even when " make install" works.  But that is a rant for
another day.

It also sounds like your problem is not so much ports as port maintainers.

thanks,

marc

On Fri, May 22, 2009 at 12:53 AM, Matt Juszczak <matt at atopia.net> wrote:
> I don't want this thread to die.  If I'm correct, this is a huge bug in
> the ports system.
>
> I've started noticing more and more that packages I build are missing
> files after they are rebuilt.
>
> For instance, I have a build box (named atlantis for the sake of this
> email): on atlantis, I build all packages with make package-recursive, and
> then install them on all boxes.  This works fine, except that over time,
> as I compile more packages, the ports system re-generates packages for
> existing built packages (for instance, if I make a nagios package, it
> recreates the apache package since that's a dependency.  If I then install
> cacti, it recreates the apache package again).
>
> This is normally no big deal, as I haven't touched my source tree, config
> options, or anything like that.  99% of the time the packages are rebuilt
> consistently.  However, since this point, I've had some php modules come
> up empty (as in my original email), and now, I'm having some other flukes
> as well.
>
> If you'll see below, somehow, fontconfig, mysql-client, and python25 got
> out of whack between my build box and a production webserver. Yet these
> are the same packages - I didn't change a thing, other than install them
> at different times.  But my build tree on atlantis has not been updated or
> changed in any manor.  This obviously occured because make
> package-recursive rebuild these packages at some point because they were
> dependencies for other packages being installed.  Except that, obviously,
> it didn't build the packages 100% identically to the time before:
>
> local$ sh check2.sh
> barfy -> fontconfig-2.6.0,1 isn't right
> barfy -> mysql-client-5.0.77_1 isn't right
> barfy -> python25-2.5.4_1 isn't right
> local$ sh check3.sh
> Server 1: atlantis
> Server 2: barfy
> Package: fontconfig
> Password:
> Password:
> 65,67d64
> < /usr/local/share/doc/fontconfig/fontconfig-user.html
> < /usr/local/share/doc/fontconfig/fontconfig-user.pdf
> < /usr/local/share/doc/fontconfig/fontconfig-user.txt
> _______________________________________________
> talk mailing list
> talk at lists.nycbug.org
> http://lists.nycbug.org/mailman/listinfo/talk
>



-- 
Freedom is nothing but a chance to be better.
Albert Camus