| Summary: | dev-tcltk/tcllib-1.16 : file collision with x11-wm/page-1.9.6-r4:0::gentoo | ||
|---|---|---|---|
| Product: | Gentoo Linux | Reporter: | Toralf Förster <toralf> |
| Component: | Current packages | Assignee: | TCL/TK Project <tcltk> |
| Status: | RESOLVED FIXED | ||
| Severity: | normal | CC: | monsieurp |
| Priority: | Normal | ||
| Version: | unspecified | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Package list: | Runtime testing required: | --- | |
| Attachments: |
dev-tcltk:tcllib-1.16:20160207-093231.log
emerge-history.txt Patch for revbump to fix file collisions |
||
|
Description
Toralf Förster
2016-02-07 09:43:59 UTC
Created attachment 424820 [details]
dev-tcltk:tcllib-1.16:20160207-093231.log
Created attachment 424822 [details]
emerge-history.txt
Yeah well. Let's set up a blocker, shall we? Created attachment 424870 [details, diff]
Patch for revbump to fix file collisions
tcllib's page binary is a parser generator. dev-tcltk/tcllib has been in tree longer than x11-wm/page and is the standard library of the language. Changing the path of its parser generator would have far-reaching effects that may be hard to track down. Changing x11-wm/page's install name to /usr/bin/pagewm or /usr/bin/page-wm is a workable alternative that requires little to no action from users or developers.
The current x11-wm/page ebuild explicitly blocks dev-tcltk/tcllib, preventing them from being on a system at the same time. This behavior is wrong. They don't implement similar functionality, so there's no reason for these packages to prevent each other from installing.
I have attached a patch for x11-wm/page-1.9.6-r5, which corrects this bug and provides a helpful message to the user indicating what changed, so they can alter their launchers and so on. Please review.
Sorry for taking so long to review this bug. @zlg: Please proceed with your patch. (In reply to Patrice Clement from comment #5) > Sorry for taking so long to review this bug. > > @zlg: Please proceed with your patch. No big deal; life happens! :) The patch has been applied via revbump, available in commit 0fe26d576d2b2093942ce6cc4a1b065c24847876 I'll go ahead and mark this bug as resolved. |