Ticket #1441 (closed defect: fixed)

Opened 7 years ago

Last modified 7 years ago

Gentoo ebuild on paludis

Reported by: MageSlayer Owned by:
Priority: minor Milestone: 4.7.0-pre2
Component: mc-core Version: 4.7.0-pre1
Keywords: Cc:
Blocked By: Blocking:
Branch state: Votes for changeset:

Description

Hi

I'd like to point that Gentoo ebuild (mc-9999.ebuild) should not does not specify
KEYWORDS="~x86" as expected

Due to that alternative Gentoo package manager paludis cannot unmask ebuild. AFAIK, omitting architectures in KEYWORDS is a undocumented hack of Portage system.

Please correct and put something like:
KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~sparc-fbsd ~x86 ~x86-fbsd" in ebuild.

BTW. It should be fine if gentoo part would be formed as an overlay with appropriate directory structure.

Thanks.

Change History

comment:1 in reply to: ↑ description ; follow-up: ↓ 2 Changed 7 years ago by slyfox

I'd like to point that Gentoo ebuild (mc-9999.ebuild) should not does not specify
KEYWORDS="~x86" as expected

Live ebuilds are not supposed to have usable(arch, ~arch) keywords.

Due to that alternative Gentoo package manager paludis cannot unmask ebuild. AFAIK, omitting architectures in KEYWORDS is a undocumented hack of Portage system.

Please correct and put something like:
KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~sparc-fbsd ~x86 ~x86-fbsd" in ebuild.

Is it? Don't you mess "" with "-*" and "~*" keywords?
I use this unmodified ebuild (copied into local overlay) in my system (paludis PM).

$ cat /etc/paludis/keywords.conf.d/mc.conf 
app-misc/mc amd64 ~amd64 *

For emerge it would be '' keyword.

BTW. It should be fine if gentoo part would be formed as an overlay with appropriate directory structure.

Maybe, keeping separate tree would be more appropriate? And leave here only README part describing path to to-be-created tree?

comment:2 in reply to: ↑ 1 ; follow-up: ↓ 3 Changed 7 years ago by MageSlayer

Replying to slyfox:

Live ebuilds are not supposed to have usable(arch, ~arch) keywords.

Not quite agree :)

Please correct and put something like:
KEYWORDS="~alpha ~amd64 ~arm ~hppa ~ia64 ~mips ~ppc ~ppc64 ~s390 ~sh ~sparc ~sparc-fbsd ~x86 ~x86-fbsd" in ebuild.

Is it? Don't you mess "" with "-*" and "~*" keywords?
I use this unmodified ebuild (copied into local overlay) in my system (paludis PM).

$ cat /etc/paludis/keywords.conf.d/mc.conf 
app-misc/mc amd64 ~amd64 *

For emerge it would be '' keyword.

Yes, I understand, but is it ok to create so many troubles? I doubt it.

Maybe, keeping separate tree would be more appropriate? And leave here only README part describing path to to-be-created tree?

It's perfect solution, as for me.

comment:3 in reply to: ↑ 2 Changed 7 years ago by slyfox

Yes, I understand, but is it ok to create so many troubles? I doubt it.

Really, nothing special here. Standard practice for live ebuilds. As not any overlay user wants user all-the-unstable-stuff to be pulled in. Moreover, with paludis PM you can unmask, say, mc-9999 in one overlay, and ignore the same in another (::overlay part in README).

Maybe, keeping separate tree would be more appropriate? And leave here only README part describing path to to-be-created tree?

It's perfect solution, as for me.

Pushed README to master as changeset:55e7db14a5290af8cea064db989a989967cdb19d

It is available at:
http://www.midnight-commander.org/browser/contrib/dist/gentoo/README?rev=55e7db14a5290af8cea064db989a989967cdb19d

This overlay is not dedicated only to app-misc/mc (would be too wasteful), but most of packages will have KEYWORDS="" to avoid accidents.

Hope, you'll find it useful.
Overlay patches welcome: http://repo.or.cz/mob.html

comment:4 follow-up: ↓ 5 Changed 7 years ago by MageSlayer

Perfect.

Only that maybe readme should contain how to add repository as system-wide? In this case paludis would sync it automatically.

P.S.
mob is an interesting idea, really.

comment:5 in reply to: ↑ 4 Changed 7 years ago by slyfox

  • Status changed from new to closed
  • Resolution set to fixed
  • Milestone changed from 4.7 to 4.7.0-pre2

Replying to MageSlayer:

Perfect.

Only that maybe readme should contain how to add repository as system-wide? In this case paludis would sync it automatically.

Ok. I'll add it slightly later (will play a little with paludis syncer).

Note: See TracTickets for help on using tickets.