net-libs/libnet AND dev-perl/libnet I'm not sure which would be the better one to rename :/
Neither? Either that or one of the two ebuilds will need to be rewritten to change the name of the package from within so that it will work, ie. simply renaming them will break them since emerge goes out and gets foo.tar.gz when you emerge dev-bah/foo. Why is this an issue?
When you type "emerge libnet" which one should emerge? Should both emerge? When I type "emerge libnet" it installs the net-libs/libnet... but this may be confusing for some other people as they may want the perl module. Maybe change dev-perl/libnet to dev-perl/libnet-perl or something... it should be extremely easy to remove the -perl ( ${P/-perl/} ) or something of the like...
The net-libs/libnet SRC_URI is invalid, anyway. Change it to http://www.packetfactory.net/${PN}/dist/deprecated/${PN}-${PV}.tar.gz Then the problem with the same .tar.gz filename is solved and you will be able to build it again :-)
Sorry, forgot to add: "for the 1.0.x package, of course
1) Just making a note: the net-libs/libnet author often changes the package name/location ... 2) Anyway, I think we should NOT rename any package. Indeed the issue really exists *only* when you type "emerge libnet" cause portage will pick the first one. So I'd suggest to pass this bug to carpaski. The quickest solution would be instructing Portage to warn the user that the ebuild he's going to merge might NOT be that he thinks it is and display the various options. -- Maurizio
I have posted to gentoo-core about this bug. Hopefully we should have some resolution soon.
The general consensus is that we should be able to keep the packages as they are. Portage needs to warn the user or stop the user and prompt for which package to actually emerge. Reassign to carpaski?
so can this be closed?
If this bug is closed, what bug has replaced it? Bug 19281?
I don't think this is considered a bug. That's why it is RESOLVED/INVALID. You can have packages with the same name in different categories.
Having two packages with the same name in different categories is not a bug, but how portage handles ambiguities ("emerge libnet") definitely is (see comment #7 to see that I'm not alone in thinking this).
