search

AOSC-Archive / autobuild3

AOSC OS package maintenance toolkit (version 3)
https://aosc.io
GNU General Public License v2.0
24 stars 17 forks source link

autobuild/alternatives not working with RPM packages #44

Closed late-in-autumn closed 8 years ago

late-in-autumn commented 9 years ago

I was building mksh and I noticed that autobuild/alternatives was working with deb packages in BuildKit but not with my RPM desktop installation. The alternatives defined in this file does not seem to take effect when installing the RPM version of the package.

Update: when hard-code update-alternatives command into postinst, I got this:

update-alternatives: error: cannot scan directory '/var/lib/dpkg/alternatives': No such file or directory

Artoria2e5 commented 9 years ago

Personally I believe auto build always writes to its scripts with alternative, at least all our current versions do.

No PM-specific scripts are supported, therefore all scripts should be global, and I am expecting the same error in RPM installation.

It seems that we should do more research on packing update-alternatives.

late-in-autumn commented 9 years ago

@Arthur2e5 I believe that this problem might lie in the RPM OS build itself then. Maybe the error message has a clue.

Artoria2e5 commented 9 years ago

AOSC-Dev/aosc-os-abbs#35 @butangmucat Look into abspec and see if alternatives have generated those pre/post actions.

late-in-autumn commented 9 years ago

@Arthur2e5 the bug lies with the rpm system itself, closing.

MingcongBai commented 9 years ago

This is actually fixed with https://github.com/AOSC-Dev/aosc-os-abbs/commit/b797120d3866ed33a558cd4e0613092355cbe57d as update-alternatives is now splitted from dpkg.

MingcongBai commented 9 years ago

However, intervention will be needed for rpm to depend on update-alternatives.

MingcongBai commented 8 years ago

In which case rpm does depend on update-alternatives. Problem solved.