Hello Paul,

Am Freitag, den 11.01.2008, 08:32 +1300 schrieb Paul Eggleton:
> Koen Kooi wrote:
> > +1 under one condition: remove the merge_feeds crap from opie image
> > recipes. Opie has no business poking in operating system files that are
> > under packagemanagement. 

As you fully know, these files weren't under package management when
merge_feeds was introduced. _Your_ feed management via packages is a
very recent thing. But we all know quite well the true reason you are
bashing merge_feeds now, so stop trying to make up excuses.

> Furthermore, /etc/ipkg/* will be re-populated
> > once people do 'ipkg upgrade', so you're back to square one.

That wasn't the behavior when merge_feeds was introduced and when Opie
images where compiled via OE for OZ. 

> Actually this is the first time I'm aware of such behaviour, and at face
> value I would have to agree with you in that it should not be doing the
> merging - if Opie-aqpkg has a problem here then it ought to be fixed
> itself rather than trying to work around it using this hack.

I fully agree, Paul. But when merge_feeds was introduced, nobody cared
enough about fixing aqpkg (or the other GUI package manager) to read
multiple config files. That was two or three years ago and I have been
proven right. Nobody has bothered to do it in all that time and
merge_feed did a valuable job to Opie users during this period.

If Koen had his wish back then, Opie users would have been left without
*any* working GUI package manager at all as the other one was even more
buggy at times.

With merge feeds (which Koen hated for his idealistic and ignorant
reasons since day one) Opie users could at least rely on aqpkg and many
did.
If someone fixes opie-aqpkg or gives some TLC to opie-packagemanager
merge_feeds has fulfilled its purpose and should be removed.

> However, if I am not mistaken this might have something to do with
> allowing users to easily enable/disable feeds. 

No, really. It was only to allow the usage of aqpkg, nothing else.
Opie-Packagemanager was absolutely unusable back then due to memory
leaks and random breakage.

I have to know, I wrote large parts of it ;) (that is btw the reason
Koen is now so vocally bashing it, don't be fooled to assume anything
else, really. He goes to great length trying to annoy me and discredit
anything I have ever done.)

> Of course we could
> accomplish the same thing without having to have the files merged
> together, but arguably if it shouldn't be modifying those files at build
> time then it shouldn't be doing it any time afterwards either. If users
> legitimately want/need to do that though then we have a bit of a conflict.
> Given Angstrom's feed structure is this something you now consider
> unnecessary?

The only sane thing would be to fix aqpkgs feed-handling or make
opie-packagemanager usable.

> For now I am happy to just do as you say and rip out that stuff from
> opie-image.bb. I will prepare a patch for that this weekend if nobody else
> gets to it before me.
> 

Ripping it out without fixing aqpkg would show Angstrom users once more
that this distro, due to its lead, focuses on developer ideals, rather
then on usability and newbie-friendliness.

It should get a new motto:
"Angstrom: The Distro For Developers, Users Beware"
-- 
Matthias 'CoreDump' Hentges 
Cologne / Germany

Webmaster of Hentges.net & Embedded Linux Developer
GPG ->  gpg --keyserver gpg-keyserver.de --recv-keys 0xAF3030D9

My OS: Debian SID: Geek by Nature, Linux by Choice




_______________________________________________
Angstrom-distro-devel mailing list
Angstrom-distro-devel@linuxtogo.org
http://lists.linuxtogo.org/cgi-bin/mailman/listinfo/angstrom-distro-devel

Reply via email to