On Mon, Feb 28, 2011 at 1:25 AM, Andreas Tille andreas@an3as.eu wrote:
Hi,
On Sun, Feb 27, 2011 at 08:09:43PM -0700, susmit shannigrahi wrote:
- I did not find a cron file in the source. It is required? If yes,
can you please pass me a sample?
The Debian packaging at svn://svn.debian.org/svn/debian-med/trunk/packages/gnumed-server/trunk/debian contains a cron.daily file - I have no idea whether Fedora is using the same mechanism but you might get an idea what to do.
Nice, thanks.
- Is it ok if I replace the directory structure */gnumed/server/* by
*/gnumed-server/*? So what is in /var/lib/gnumed/server in debian will be in /var/lib/gnumed-server. Do you think this may break something?
I can not imagine any severe breakage - perhaps adjusting pathes in some scripts. Do you see any strong reason for this rename? Do you think the decision for /var/lib/gnumed-server is suboptimal?
The reason I did this because fedora packaging naming guideline says: "When naming a package, the name should match the upstream tarball or project name from which this software came.", which, in this case, is gnumed-server and also, I get to use %{name} macro everywhere.
However, packaging guideline also says "If this package has been packaged by other distributions/packagers in the past, then you should try to match their name for consistency.".
So, I am fine with both naming schemes, just need to make a decision which one to use. :)
Thanks. [1] http://fedoraproject.org/wiki/Packaging/NamingGuidelines#General_Naming