Public SourceMage Discussion List

[Eric Sandall <eric AT sandall.us>]

Quoting Arwed von Merkatz <v.merkatz AT gmx.net>:
<snip>
> What about updates without a bug? E.g. I update libmpeg2 knowing that
> all spells using it will need to be recompiled due to an ABI change.
> This doesn't happen often enough to warrant the onslaught of triggers
> we'd need to prevent it. But it should be documented, so we need a way
> to get that info to the people doing the actual stable grimoire
> releases.
> I'm not sure what the best option is here. One option would be a
> text file in the spell describing such things, another would be filing
> bugs on such updates explicitly and get those to the QA team.

Talked about in the linux-pam bug:
http://bugs.sourcemage.org/show_bug.cgi?id=680

Short:
A versioned trigger based on the minor number (2.4 -> 2.6, e.g.) should be
enough, and only parse "valid" VERSION tags (such as x.x.x, not BetaIII-42b 
and
such). Then we could have:

wget/TRIGGERS:
on_minor_update gettext cast_self

*/TRIGGERS:
on_minor_update linux-pam cast_self

Then, only when linux-pam goes from 0.76 -> 0.77 would a trigger be caused, 
and
not just any recompile of Linux-PAM.

openssh/TRIGGERS:
on_revision_update openssl cast_self

This way openssh would only be updated when openssl goes from 0.9.6 -> 0.9.7
(since their revisions change the shared library names), but not 0.9.6a ->
0.9.6b (hopefully).

-sandalle

--
Eric Sandall                     |  Source Mage GNU/Linux Developer
eric AT sandall.us PGP: 0xA8EFDD61  |  http://www.sourcemage.org/
http://eric.sandall.us/          |  SysAdmin @ Inst. Shock Physics @ WSU
http://counter.li.org/  #196285  |  http://www.shock.wsu.edu/

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.