On 2016-12-21 12:48, Rene Gollent wrote:
On Wed, Dec 21, 2016 at 10:27 AM, kallisti5 <kallisti5@xxxxxxxxxxx> wrote:Check in an entire kit + PM support code and nobody reviews the thousands
and
thousands of lines of code committed.
Through all of this, I wish I tried to write an app using the package kit
sooner :-(
I'm sorry, but this is an utter and complete lie. All of the package
kit/infrastructure development happened in the open in github repos
that were tracked on the commits list, and there were multiple interim
blog posts about progress. People did in fact comment on/have
discussions about said commits long before they were merged back, you
simply didn't care at the time. At the end of the day, like it or not,
this is a complicated problem, and is invariably going to have
complicated interactions a result. In the case of an update for
instance, the kit has to be able to inform a caller when conflicts
occur, what they were, details of the possible solutions, etc. in a
way that's independent of the type of application/user interface
involved, as well as providing a way to tell it which outcome is
desired.
That's simply going to require a lot more work than
update_the_whole_os_for_me_because_im_lazy(), no ifs ands or buts, as
is inevitable in any case when dealing with the user is involved.
There are multiple applications in the system using the package kit,
written by different people, so clearly others have managed to
understand how to work with it.
