On 10/13/2014 20:21, Nikola M. wrote:
I still wait for your reply on idea that every Hipster update has new
'entire' version changed, so someone testing could always update to
exact date and packages state to re-create environment where bug started
to happen.
Hello.
Now entire is generated on the base of existing packages in the
repository. So it's technically hard to update it before publishing new
packages. If we update entire after publishing new package, we have two
problems.
1) New packages are not immediately available (before updating entire).
2) Before publishing entire we can't guarantee that it's installable.
Publishing uninstallable entire seems damn wrong.
I think about the following. What if we create periodic task that
generates entire on the base of current state of the repository,
performs some heuristic checks on it, publishes it to separate
repository, temporary add this publisher and try to pkg update -n
entire? So we can check that current entire is installable and perhaps
even publish it to the main repository. But I'm still not convinced that
having non-empty entire incorporation is a good thing.
--
Best regards,
Alexander Pyhalov,
system administrator of Southern Federal University IT department
_______________________________________________
oi-dev mailing list
[email protected]
http://openindiana.org/mailman/listinfo/oi-dev
