Re: [gentoo-dev] Bunch of bugs (nothing major - skip if you're not interested)

[Mikael Hallendal <hallski@gentoo.org>]

Den 15 Aug 2001 05:09:11 +0000 skrev Don Davies:
> Sigh,

Hi! :)

> After trying to enlist help in the iRC channel to fix these,
> the impression was made that a team meeting had to take
> place before bugs could be fixed.  I understand the
> underlying principle of not wanting to tread over other 
> peoples territory.. but in reality we're talking about typos
> and small build fixes.  If these cannot be immediately fixed
> and need a developer conference to resolve.. then well..
> Good Luck when the portage tree reaches several thousand
> packages.  Is there no interest in fixing old stuff or what?

Ok, look like you got hold of the wrong guy ...
The team concept shouldn't be "used" like this, it's more to take some
burden from the shoulders of Drobbins and Achim.

Generally I do believe that fixes of this sort is better mailed here
than brough up on IRC. Because for example when there are = and one my
think it should be >= there _might_ be a reason why the developer has
done it this way. I think in those situation it's correct to say that it
should be brought to the developer responsible (or the team) for that
ebuild, therefor it's best to send it to the list.

If the error is of the typo-kinda way like 'fretype instead of freetype'
it should be fixes asap by any developer around, these kind of problems
shouldn't be a problem bringing up on IRC.

This doesn't say you can first try to ask on IRC.

> 1.  the dev-lang/php/* ebuilds are erroneously referencing
> a *specific revision* of freetype-1 in the DEPEND line.  These
> lines should have the = replaced with >= or better yet the
> new ~ syntax makes sense here.

So, does anyone knows why it's = instead of >=? (achim, any special
reason for this). I will for now use ~ instead.

> 2.  The exact same bug is present in the media-libs/libgd
> ebuild.  It needs to say >= freetype-1-r1 not =freetype-1-r1

Since it's here to I get the feeling that it is a reason why it's exact
one version. However there shouldn't be no problem with a later
revision. The ~ syntax is relativly new though and many packages will
probably need to be updated to use this. 

Perhaps it's because of some incompatiblity issues between freetype-1
and freetype-2.
 
> 3.  The minicom ebuild in the tree doesnt build complaining of
> a bad ko.mo file.  I dont know if gettext-0.10.39 would solve the
> problem, but even as of the latest rc6 build image, 0.10.38 is
> being used. If somebody will add this quick hack/fix to the
> bottom of minicom's src_unpack, it will at least compile and install:
> 
> cp po/Makefile po/Makefile.orig
> cat po/Makefile.orig | sed -e "s:ko.mo: :" > po/Makefile

Could someone please test this? (ryan?)
I'll add a todo for this.

> 4.  The x11-wm/bbkeys ebuild is badly broken.  Im afraid it
> needs to be reworked.. some parts are just plain wrong. For
> example the part where it tries to use DESTDIR for a Makefile
> that doesnt have such a construct.  Its only 1 bin for that part
> anyway.  I have a working one, which Ill post to gentoo-ebuild.

>From what I read, lordjoe has fixed this now.

> Most of this could have been fixed in 5 mins had somebody 
> showed interest in doing so.  Instead typos need a formal report?
> I dont mean to sound overly sarcastic, but surely we neednt go
> though this excercise in order to get a few small bugs tidied up.

IRC is a nice medium many times, but not everyone that's in there has
the time to follow it all the time. The answer you recieved is clearly
wrong imho. The answer that whoever you talked to should have given you
should be, "Could you please put this in a mail and send to gentoo-dev
because I haven't got time to look into this right now".

Thanks for the reports (all have been dealt with except for the minicom
which I've added a todo about),

Regards,
  Mikael Hallendal