Ah, yes, I see now that you have followed the packaging guidelines. I did not
know they recommended avoiding relocatable packages, and I also did not know
that they recommended against installing packages in /opt. Now I understand. I
retract my suggestion. Thank you for your quick response, and thanks again for
packaging scid into an rpm.
I always thought that it was a bad idea to install anything in /usr/bin because
you might accidentally overwrite a system command. For example, you could write
a package that installs an executable named "ls." What prevents you from doing
that? Do you simply have to be very careful?
----- Original Message -----
From: "Mikhail Kalenkov" <mikhail.kalen...@gmail.com>
To: scid-users@lists.sourceforge.net
Sent: Saturday, May 10, 2014 7:02:52 AM
Subject: Re: [Scid-users] Relocatable SCID RPM for Linux
Hi James,
I made scid rpm package following "Fedora Packaging Guidelines" [1].
It recommends to avoid relocatable packages. For instance they say
that relocatable package can not be installed by yum. I guess it is
strong argument against relocatable package.
I do not see any inconvenience in keeping scid in /usr, especially if
you install it using package manager.
[1] https://fedoraproject.org/wiki/Packaging:Guidelines
Best regards,
Mikhail Kalenkov.
2014-05-10 1:21 GMT+04:00 James K. Williams <james.k.willi...@comcast.net>:
> This is a message to Mikhail Kalenkov, who was kind enough to build a scid
> RPM for Fedora available at http://katrine.lpi.ru/kalenkov/.
>
> Thank you very much for providing the RPM. It is much, much simpler than
> having to build scid from source code. But I have a suggestion. Can you
> please modify the package to be relocatable? Right now, it installs scid in
> /usr/bin. I would prefer to install it in /opt, which is the preferred
> directory in the Linux FHS standard for installing third-party applications.
> I like to preserve /usr/bin and /bin for operating system user-level
> commands.
>
> The current RPM is unrelocatable, which you can verify by typing
>
> rpm -qi scid
>
>
>
> ------------------------------------------------------------------------------
>
> Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
> • 3 signs your SCM is hindering your productivity
> • Requirements for releasing software faster
> • Expert tips and advice for migrating your SCM now
> http://p.sf.net/sfu/perforce
> _______________________________________________
> Scid-users mailing list
> Scid-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/scid-users
>
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users
------------------------------------------------------------------------------
Is your legacy SCM system holding you back? Join Perforce May 7 to find out:
• 3 signs your SCM is hindering your productivity
• Requirements for releasing software faster
• Expert tips and advice for migrating your SCM now
http://p.sf.net/sfu/perforce
_______________________________________________
Scid-users mailing list
Scid-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/scid-users
