RDNN package name

[cassidyjames]

Looks like #85 took care of everything else, but we still have maya-calendar as the package name here.

---

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

[4jNsY6fCVqZv]

Where exactly in the code do changes to the package name have to be made?

By the way: Is there a reason why the maya.gresource.xml still exists under this name? Or can I rename it safely?

[cassidyjames]

@4jNsY6fCVqZv I think packaging changes need to be made in the deb-packaging branch, but we'd need to make sure it is not going out to Hera users—which will require coordination with @danrabbit and/or @tintou.

That file should be able to be renamed as long as any code referencing it (i.e. in meson) is also updated—but it would be a separate branch from any packaging changes.

[4jNsY6fCVqZv]

@cassidyjames Will Daemon be enough at io.elementary.calendar-daemon.desktop.in? Or should there be a linguistic reference to the calendar? Currently it's still Maya Daemon. I wonder if it is important to replace all the Maya references bit by bit. What are your thoughts on this as a team?

@danrabbit @tintou Could you imagine to teach me how to make this transition?

[danirabbit]

@4jNsY6fCVqZv several small branches are always going to be easier to review and merge :)

The name field for the daemon .desktop shouldn't actually show anywhere, so it should be fine to rename it to anything really. But in that case that it somehow does show somewhere, I think "Calendar Daemon" would be most appropriate

I created a deb-packaging-bionic branch to make sure we don't interfere with bionic builds unintentionally.

If you look at Camera, you see how there are transitional packages defined here: https://github.com/elementary/camera/blob/deb-packaging/debian/control#L21

So that needs to be done for every package that calendar provides

[danirabbit]

Here's a much simpler example. I'm not 100% certain, but I think this should do it: https://github.com/elementary/greeter/pull/448/files

[4jNsY6fCVqZv]

@danrabbit Thanks a lot for the hints!

I see the following packages: maya-calendar, maya-calendar-common, maya-calendar-daemon, libmaya-calendar0, libmaya-calendar-dev, maya-calendar-plugin-google, maya-calendar-plugin-caldav.

1. Is it really necessary to keep all the (transitional) packages? Or can debian/control be cleaned up a bit here?
2. Is it just a matter of changing the packages in debian/control, or do I need to make appropriate changes for all maya-calendar called files here as well? https://github.com/elementary/calendar/tree/deb-packaging/debian

[4jNsY6fCVqZv]

I still want to work on a solution. Are there people who can support me in clarifying my open questions?

[fabiozaramella]

@4jNsY6fCVqZv I think @tintou might answer you questions