package name is unduly confusing and will likely cause conflicts

[matt.wartell]

Given https://answers.launchpad.net/nautilus-elementary/+question/128553 and http://ubuntu.stackexchange.com/questions/5403/no-nautilus-elementary-in-maverick-rc there's pretty good evidence that this package is hard to install properly.

I expect this comes as a result of wanting your package fork to drop-in as a replacement for the official nautilus package. This "name overloading" is hurting usability now and will possibly get worse as Canonical package nautilus and ammonkey package nautilus are updated.

[ammonkey (am-monkeyd)]

"there's pretty good evidence that this package is hard to install properly."

Not really if you know how to install ppa packages, the procedure is pretty standard like any other development ppa, the package provided in the PPA overwrite the default package proposed elsewhere official repository, other package etc.

"will possibly get worse as Canonical package nautilus and ammonkey package nautilus are updated."
Well i maintain theses packages since gnome 2.28 so ..... I think i am used to it and our users too.

As long as gnome desktop don't provide a way to choose your default filemanager we don't have any other options than to replace the nautilus package. Remind me the old time of the web browsers where you can't configure your default web browser. The same problematic occur with other filemanagers like pcmanfm etc, they have to replace nautilus binaries for a decent integration in the gnome desktop.

Your request is just invalid, renaming the package won't solve anything.

[matt.wartell (matt-wartell+lp)]

fair 'nuff; thanks for the explanation of where the underlying issue lies.