| To: | Ken McDonell <kenj@xxxxxxxxxxxxxxxx>, PCP <pcp@xxxxxxxxxxx> |
|---|---|
| Subject: | Re: [pcp] Duplicate Names in the PMNS - seeking consensus |
| From: | Mark Goodwin <mgoodwin@xxxxxxxxxx> |
| Date: | Mon, 19 Jan 2015 11:06:07 +1100 |
| Delivered-to: | pcp@xxxxxxxxxxx |
| In-reply-to: | <54BA00E9.7050504@xxxxxxxxxxxxxxxx> |
| References: | <54BA00E9.7050504@xxxxxxxxxxxxxxxx> |
| User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:31.0) Gecko/20100101 Thunderbird/31.3.0 |
On 01/17/2015 05:27 PM, Ken McDonell wrote: [...] This does not work at all "as is". It can be made to work, but that involves changing scores of source files ... the result is an ugly hack hiding a git branch and I'm not going to commit that to the dev branch. On reflection, I think there are 2 alternatives: 1. change the default behaviour to allow duplicates and strip out all the "no duplicates" stuff, or 2. drop all pretence at supporting duplicate names and rip out the associated non-working stuff. Thoughts? I think it'd be good generally, and from the back compat viewpoint, e.g. following namespace migrations and PMDA pmns updates, etc. But how would pmTraversePMNS() work? What other problems are there? Cheers -- Mark |
| <Prev in Thread] | Current Thread | [Next in Thread> |
|---|---|---|
| ||
| Previous by Date: | pmda cache permissions issue, Mark Goodwin |
|---|---|
| Next by Date: | Re: pmda cache permissions issue, Frank Ch. Eigler |
| Previous by Thread: | Duplicate Names in the PMNS - seeking consensus, Ken McDonell |
| Next by Thread: | Re: [pcp] Duplicate Names in the PMNS - seeking consensus, Ken McDonell |
| Indexes: | [Date] [Thread] [Top] [All Lists] |