Re: [E-devel] examine doesn't build

[Brian M. <bri...@gm...>]

On Sunday 05 February 2006 22:31, you wrote:
> On 2/6/06, Brian Mattern <bri...@gm...> wrote:
> > the notebook API changed and examine hasn't been updated yet.
>
> This was obvious indeed!
>

The last two lines of output are:
=2E..:432:"undefined reference to `ewl_notebook_tabs_position_set'... =A0and
=2E..:433: undefined reference to `ewl_notebook_tabs_alignment_set'...

This was just hours after an EWL commit that says:

=2D rename notebook2 to notebook.
=2D this is API breakage. you now use the normal container functions to
=A0 append/prepend/insert widgets to the notebook

So sure, not completely obvious if you don't have a lot of experience with=
=20
compiler errors, but the commit log was fairly clear.

Also, he explicitly asked "what has happened", so I let him know...


> > I would highly recommend following CVS commits and updating when
> > something is added that you want to try out rather than just blindly
> > updating everything every day.
>
> Not many people have the time (or knowledge) to follow CVS commits
> every day and on top of that patching what hasn't been updated.
> There's a fine line between developer and enthusiastic user who wants
> to get the latest E. Of course your recommendation is good but it's
> easier to update blindly once you know that a certain number of
> commits have been done without going into the details of particular
> commits.

I understand that it takes an extra amount of time to actually follow=20
development, but then again, you might learn something about it. I definite=
ly=20
don't expect users to patch the things that haven't been updated.

I do want encourage people to become either a bit more knowledgable or at=20
least a bit more patient. I don't want to discourage people from using e17.=
 I=20
think the enthusiasm is great. However, at this time the user base VASTLY=20
outnumbers the developer base, and we spend a LOT of time helping people=20
compile things.

>
> > Keep in mind that this is CVS and not a release system, and as
> > developers, we reserve the right to break things.
>
> Agreed. But bear in mind that as a user we reserve the right to inform
> politely the developers that they broke things and if possible to fix
> them at their convenient time. :-)
>

Sure, and polite bug reports are often helpful. But I just want to reiterat=
e=20
that this is development code. If we change an API it may take a few days t=
o=20
get everything using that updated.=20

Also, its entirely possible someone will commit something that is incomplet=
e,=20
along with a message stating "don't use this yet, it will hose your box", a=
nd=20
I'd prefer not to have dozens of reports the next day of people who hosed=20
their boxes because they had to get their E fix that day.

=2D-
rephorm