Ticket #702 (closed defect: fixed)

Opened 11 years ago

Last modified 11 years ago

exheres-0: make pkg_* phases aware of upgrade,downgrade,reinstall,uninstall status

Reported by: pioto Owned by:
Priority: Sometime Milestone: EAPI exheres-0
Component: repositories/e Version: scm
Keywords: Cc:
Blocked By: Blocking: 731
Distribution: Exherbo

Description (last modified by pioto) (diff)

As mentioned on  https://bugs.exherbo.org/show_bug.cgi?id=128, we need to have some way for various exheres phases to know whether they are being called on a package that is being upgraded/downgraded, reinstalled, or uninstalled.

I think the various suggestions have included:

  • Make some additional environment variable available in those phases.
  • Provide an additional function which can give this information to the exheres (presumably via a pipe command?).

Change History

comment:1 Changed 11 years ago by pioto

  • Description modified (diff)

comment:2 follow-up: ↓ 3 Changed 11 years ago by ciaranm

Define upgrade/downgrade. This gets very messy with slots (especially changing slots) and roots. Is it sufficient to provide a list of IDs that will be replaced by this install?

comment:3 in reply to: ↑ 2 Changed 11 years ago by pioto

Replying to ciaranm:

Define upgrade/downgrade. This gets very messy with slots (especially changing slots) and roots. Is it sufficient to provide a list of IDs that will be replaced by this install?

Hmm, I think that should be sufficient. If we're replacing the same thing as ${CATEGORY}/${PNVR}:${SLOT}, then we're reinstalling, otherwise we're up/down-grading, correct?

Well, what about the uninstalling case?

comment:4 Changed 11 years ago by pioto

Oh, yeah. For uninstall / new install, the list would be empty.

comment:5 Changed 11 years ago by ciaranm

Except that you might have foo/bar-1:2 and foo/bar-2:1 installed, and are installing foo/bar-2:2. What's that?

comment:6 Changed 11 years ago by pioto

... stupid upstream & stupid exheres maintainer?

comment:7 Changed 11 years ago by ciaranm

Yeah, but we have to deal with it.

comment:8 Changed 11 years ago by ciaranm

  • Blocking set to 714

comment:9 Changed 11 years ago by ciaranm

  • Blocking changed from 714 to 731

comment:10 Changed 11 years ago by ciaranm

  • Status changed from new to closed
  • Resolution set to fixed

4993721605c

Note: See TracTickets for help on using tickets.