Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 263787 - app-text/foo-123-bar-2.0017a_p-r5 valid according to pms, invalid according to portage
Summary: app-text/foo-123-bar-2.0017a_p-r5 valid according to pms, invalid according t...
Status: RESOLVED DUPLICATE of bug 227265
Alias: None
Product: Documentation
Classification: Unclassified
Component: [OLD] Portage Documentation (show other bugs)
Hardware: All Linux
: High normal (vote)
Assignee: PMS/EAPI
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-03-25 22:12 UTC by Peter Alfredsen (RETIRED)
Modified: 2009-03-25 22:42 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Alfredsen (RETIRED) gentoo-dev 2009-03-25 22:12:34 UTC
<zong_sharo> hmm, does any gentoo's package manager accepts package name like foo-123-bar
<zong_sharo> pms defines this as a valid name
<zong_sharo> category/foo-123-bar-2.0017a_p-r5
<zong_sharo> like this
<zong_sharo> one
<reavertm> zong_sharo: you should take pms with some grain of salt
<zong_sharo> some?
<loki_val> zong_sharo: that looks valid.
<zong_sharo> yeah, this is completely in pms spec
<zong_sharo> but, does anyone really accepts this?
<reavertm> well, try if you're curious
<loki_val> portage does not accept this:
<loki_val> Invalid ebuild name: /home/pa/poppler-overlay/app-text/foo-123-bar/foo-123-bar-2.0017a_p-r5.ebuild
Comment 1 Ciaran McCreesh 2009-03-25 22:16:04 UTC
Hrm, why doesn't Portage accept this? Which bit specifically does it hate?
Comment 2 Santiago M. Mola (RETIRED) gentoo-dev 2009-03-25 22:40:43 UTC
Portage forbids names with version-like parts.

pym/portage/versions.py:
for x in myparts[:verPos]:
	if ververify(x):
	    pkgcache[mypkg]=None
	    return None
	    #names can't have versiony looking parts

Comment 3 Santiago M. Mola (RETIRED) gentoo-dev 2009-03-25 22:42:24 UTC

*** This bug has been marked as a duplicate of bug 227265 ***