Re: [PATCH 1/3] avahi.inc: rename package to use avahi to instead of avahi-daemon

[Anders Darander <anders@chargestorm.se>]

* Hongxu Jia <hongxu.jia@windriver.com> [141113 02:44]:

> On 11/13/2014 09:28 AM, Hongxu Jia wrote:
> > On 11/12/2014 06:27 PM, Koen Kooi wrote:
> >>> Op 11 nov. 2014, om 11:52 heeft Hongxu Jia 
> >>> <hongxu.jia@windriver.com> het volgende geschreven:

> >>> The package avahi does not exist, as SUMMARY said, we should
> >>> use avahi-daemon to instead. It avoids the do_rootfs failure
> >>> while IMAGE_INSTALL += "avahi"

> >>> For compatibility, let avahi to provide avahi-daemon.
> >> As stated before:

> >> 1) Fix your IMAGE_INSTALL

> > Could you describe what's wrong with IMAGE_INSTALL?
> > I have no idea about it.

Koen means that you should use
IMAGE_INSTALL_append += "avahi-daemon"
and not avahi... (I.e. package name, not recipe name).

If you still insist on creating a package named avahi, you might as well
create avahi as an empty package, RDEPEND'ing on all sub-packages.

> >> 2) This breaks upgrade paths

> >> Do you *really* want to break existing installs just so you can 
> >> pretend that your recipename==package name assumption isn't wrong?

> > What does *upgrade paths* means?


> Do you mean use package management to upgrade the
> package, such as "smart upgrade". If yes, I think you are right,
> we could drop patch 1/3 and 2/3.

Yes, that's exactly what Koen talks about when it comes to ugrade paths.

Cheers,
Anders

-- 
Anders Darander
ChargeStorm AB / eStorm AB