[paludis-dev] [Paludis] #1283: portageq emulation for envvar not implemented - sys-apps/portage-2.2.1

Paludis trac-paludis at exherbo.org
Sat Aug 24 08:16:50 UTC 2013


#1283: portageq emulation for envvar not implemented - sys-apps/portage-2.2.1
------------------------------+--------------------
    Reporter:  void           |      Owner:
        Type:  ebuild-defect  |     Status:  closed
    Priority:  Sometime       |  Milestone:
   Component:  core/paludis   |    Version:  1.4.0
  Resolution:  upstream       |   Keywords:
  Blocked By:                 |   Blocking:
Distribution:  Gentoo         |
------------------------------+--------------------

Comment (by kentnl):

 I'm not so sure about that.

 A package is imo, entitled to call functions and execute code, that that
 package also ships.

 This is what I believe portage is doing, a self-test. Which is legitimate,
 because portage provides the 'portageq' program.

 If it were any other ebuild, I'd say you had a point, because that would
 be invoking things beyond the scope of that package.

 However, when the package is portage, the lines blur.

 and its not calling 'portageq SYNC', its just 'portageq envvar SYNC'.

 Its only a problem because instead of executing the program that it was in
 the process of installing, it calls paludis instead, in essence, the
 compatibility shim paludis provides interferes with the package simply
 testing itself.

 I guess the portage ebuild **could** specialcase the `type portageq` to be
 `type -f portageq`, which I'd imagine largely avoid calling paludis if
 `portageq` was a function instead of a program.

-- 
Ticket URL: <http://paludis.exherbo.org/trac/ticket/1283#comment:2>
Paludis <http://paludis.exherbo.org/>
Paludis, the Other Package Mangler


More information about the paludis-dev mailing list