[gobolinux-users] silly Freshen message

[Michael Homer]

On 10/4/07, Isaac Dupree <isaacdupree at charter.net> wrote:
>
> ]Freshen --no-binaries -U
> [...]
> Freshen: Upgrading 5/40...
> [IUR] LibPNG 1.2.20-r1
>   1.2.16-r3
> Freshen: Upgrading LibPNG...
> Freshen: First preference binary, no binary. #<-****HERE***
> Freshen: Got a recipe though.
> Freshen: Feeding this off to Compile...
> [...]
>
> If the user requested "no binaries", how does it make sense to say
> "first preference binary"?
Yeah, ok. That message is from the "preference=binary,recipe" line in
Freshen.conf, but it should probably be dropped when one or the
other's been turned off.
>
> Also in the list that `Freshen --no-binaries` first shows, everything is
> green (which means "only Recipe available"), even the packages that
> Freshen without --no-binaries shows as blue (which means "Recipe+Binary
> available").  I suppose this means Freshen doesn't even look for
> binaries when you don't want them (which makes sense).
Correct. Whichever one is disabled is ignored completely for all
purposes (although cached dependency files may be used). I will see
about fixing that.
> P.S. Some recipes (such as GHC-Bin) are for (third-party) binaries (that
> likely use Makefiles).  Of course, they have i686 and other
> arch-specific sections in the recipe.  In Freshen's view they are
> "Recipe" not "Binary"...
"Binary" is possibly an unfortunate choice of terminology still there
for historical reasons; I wanted to avoid the term "package" at this
level and go with something unambiguous.

It doesn't care what the recipe does, just that it's a recipe and that
it can have Compile called on it - if the recipe happens to install a
third-party binary package from there, that's its business. If there
were some way to detect the difference between those two I guess it
would be possible to exclude them, but I definitely don't want to do
it heuristically.
-Michael