On 12/17/2009 09:15 AM, Martin Sivak wrote:
> Hi,
>
>> It's not that it'd be hard to implement, it's that the scope of this
>> automatic driver disk thing just keeps increasing to involve more and
>> more stuff all the time. We have mechanisms for specifying updates
>> images. What's wrong with using one of those?
>
> Nothing if you ask me. Partners would tell you something different
> though. It is usually something along the lines of "bad customer
> experience" and "revenue loss". And you haven't seen the proposals
> for automatic shell script execution... Or maybe you did..
The partners know how to file a second request for a second feature, and
they'll do it if we have our partner manager tell them to.
> I have to fight a lot to avoid the features which are useless and
> avoidable using mechanisms we already have, so I'm getting really
> tired and annoyed when I have to fight here too. Especially when
> everybody generally hates the feature... nobody reviews it for two
> weeks and then all of a sudden, I'm asked to rewrite half of the
> code...
I don't see a single instance on this whole subject when you've posted
without getting a response for more than a week. In most cases it's
been within a day. I know that review can be a difficult process,
especially with such a large chunk of code, but hyperbole really is
not helping here.
> Talking about libarchive, their documentation is a mess and could use
> some help too (I wasn't just complaining, I actually looked at it and
> I like the concept, but I have to figure out the small details
> first...)
The API is not very hard to figure out from the headers; I wrote a test
app at FudCon using it in 10 or 15 minutes.
--
Peter
I'd like to start a religion. That's where the money is.
-- L. Ron Hubbard to Lloyd Eshbach, in 1949;
quoted by Eshbach in _Over My Shoulder_.
_______________________________________________
Anaconda-devel-list mailing list
Anaconda-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/anaconda-devel-list
