Hi all.
I have integrated Rich's modifications to upgrade the Player package to 3.0.0. I ran into a problem I'd like to discuss here. Toby, please have a look as you might give some insight as upstream developer.
By default the config files are now installed to /usr/share/player/config. For Player 2.1.0 the configs were installed to /etc/player/config, which seems more reasonable.
What is the reasoning for moving them? Since this are regular config files which might be modified I see no reason to put them in /usr/share. The Linux FHS states that /usr/share is for "all read-only architecture independent data files" (cf. http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE26). It seems that this does not apply to the config files. What do you think?
Regards, Tim
Hi,
On ۰۹/۱۰/۲۳ 12:54, Tim Niemueller wrote:
Hi all.
I have integrated Rich's modifications to upgrade the Player package to 3.0.0. I ran into a problem I'd like to discuss here. Toby, please have a look as you might give some insight as upstream developer.
By default the config files are now installed to /usr/share/player/config. For Player 2.1.0 the configs were installed to /etc/player/config, which seems more reasonable.
What is the reasoning for moving them? Since this are regular config files which might be modified I see no reason to put them in /usr/share. The Linux FHS states that /usr/share is for "all read-only architecture independent data files" (cf. http://www.pathname.com/fhs/pub/fhs-2.3.html#PURPOSE26). It seems that this does not apply to the config files. What do you think?
Just my personal opinion: At the first look, I thought that the new place is not suitable for config files; but after a very brief look at them, I feel that the new place is not bad too. I think these configuration files are not there to be modified. They are created for special purposes (e.g. a specific robot), so someone with new requirements should create a new config file and so these config files are not going to be modified. If that is correct, so putting these config files in /usr/share is OK. But the user must not put his own configuration files in that directory. So, either he should be able to put his config files in any directory (probably somewhere in his home directory) or below /etc.
If all what I said applies to these configuration files, I think they completely satisfy "read only architecture independent data files".
Thanks, Hedayat
Regards, Tim
On 23.10.2009 00:14, Hedayat Vatankhah wrote:
Hi,
Hi Hedayat, thanks for the quick reply!
If all what I said applies to these configuration files, I think they completely satisfy "read only architecture independent data files".
I thought about your reasoning. But there are device files and the like specified in the config files which may change. Additionally to create a new configuration most of the time you start by copying an existing config file, being able to do this in the very same directory makes things simpler. Additionally having some config files in /usr/share and some in /etc seems odd.
I'd like to hear more opinions, but I tend to the /etc solution atm.
Regards, Tim
On ۰۹/۱۰/۲۳ 02:21, Tim Niemueller wrote:
On 23.10.2009 00:14, Hedayat Vatankhah wrote:
Hi,
Hi Hedayat, thanks for the quick reply!
:)
If all what I said applies to these configuration files, I think they completely satisfy "read only architecture independent data files".
I thought about your reasoning. But there are device files and the like specified in the config files which may change.
Well, if they are going to be modified themselves then /usr is not an appropriate location.
Additionally to create a new configuration most of the time you start by copying an existing config file, being able to do this in the very same directory makes things simpler. Additionally having some config files in /usr/share and some in /etc seems odd.
If player allows; people will probably put their own config files in their home directories or something like that. There is no need to put them in /etc.
Anyway, thanks for your efforts; Hedayat
I'd like to hear more opinions, but I tend to the /etc solution atm.
Regards, Tim
Hi, Those config files are basically examples of how to set up config files, or starting points to bootstrap from. At least this is how I believe most people use them. Thats why /usr/share was chosen. Possibly they should be in /usr/share/doc?
Toby
2009/10/23 Hedayat Vatankhah hedayatv@gmail.com
On ۰۹/۱۰/۲۳ 02:21, Tim Niemueller wrote:
On 23.10.2009 00:14, Hedayat Vatankhah wrote:
Hi,
Hi Hedayat, thanks for the quick reply!
:)
If all what I said applies to these configuration files, I think they
completely satisfy "read only architecture independent data files".
I thought about your reasoning. But there are device files and the like specified in the config files which may change.
Well, if they are going to be modified themselves then /usr is not an appropriate location.
Additionally to create a
new configuration most of the time you start by copying an existing config file, being able to do this in the very same directory makes things simpler. Additionally having some config files in /usr/share and some in /etc seems odd.
If player allows; people will probably put their own config files in their home directories or something like that. There is no need to put them in /etc.
Anyway, thanks for your efforts; Hedayat
I'd like to hear more opinions, but I tend to the /etc solution atm.
Regards, Tim
Fedora-robotics-list mailing list Fedora-robotics-list@redhat.com https://www.redhat.com/mailman/listinfo/fedora-robotics-list
robotics@lists.fedoraproject.org