> The second big issue I had was that "generate.py source-each"
wouldn't
> work
> because my config.json didn't know about it. I had to manually add
> "source-each" to the export list before it could be used.
Yeah, that's a good one. I forgot to mention this in the blog
post, and I
would have loved to see a bug for it opened.
I've been awaiting the resolution of the bug that got re-opened. If
this was going to remain, I would have mentioned that this need should
be documented.
Very good.
(My post was, after all, a response to query for opinions, so I felt
free to express mine. :-) )
Fair enough. I wasn't getting that you were targeting the average user
here (someone who deploys released versions only).
For people working on trunk it should go without saying that they
may bump
into such issues, which are easily resolved with a post on the mailing
list. (Of course I also expect those guys to regularly read the
weeklies...).
Yup. I work with trunk, and I watch bugs, commit messages, and the
weeklies. Most of the time, I even remember what I read. :-) I also
was able to solve my own problem. My comments are not pertaining to us
trunkies, but rather to the unsuspecting less knowledgeable user who
has to make obtuse changes for no clear benefit.
I don't think we will be able get away without changes to existing
config files in general, so we have to have a strategy here. And I for
one was an "unsuspecting less knowledgeable user" myself with many
software packages I used during my lifetime, and I was quite happy with
instructions like "apply <foo> to <bar>" to get a new version working.
But of course, YMMV.
T.
------------------------------------------------------------------------------
All the data continuously generated in your IT infrastructure contains a
definitive record of customers, application performance, security
threats, fraudulent activity and more. Splunk takes this data and makes
sense of it. Business sense. IT sense. Common sense.
http://p.sf.net/sfu/splunk-d2dcopy1
_______________________________________________
qooxdoo-devel mailing list
qooxdoo-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/qooxdoo-devel
