Re: Q: Location of copyrighted ROM images for emulator packages?
On Sun, Feb 22, 1998 at 12:07:46PM -0600, Manoj Srivastava wrote:
> Hi,
> >>"Marcus" == Marcus Brinkmann <Marcus.Brinkmann@ruhr-uni-bochum.de> writes:
>
> Marcus> On Sat, Feb 21, 1998 at 06:36:20PM -0600, Manoj Srivastava
> Marcus> wrote:
> >> Hi,
> >>
> >> If the ROMs are adta, and not conf files, then how do we solve the
> >> issue of never overwriting a user provided rom? If you create a
> >> zero length file in /var/lib/Blah, and I overwrite it, and then I
> >> upgrade or re-install, are my chages gone? If so, it is a bug in
> >> the package.
>
> Marcus> As I see it, policy does not state that conf files have to
> Marcus> reside in /etc. And not all files in /etc are conf
> Marcus> files. There is in fact only a semi strong correlation between
> Marcus> /etc and conf files.
>
> AARRGGHH. This is WRONG> Not only did you not read the policy
> manual, you blithely ignored the policy when someone quoted it for
> you. Please do not spread misinformation. Policy is clear on this
> regards.
I'm sorry for this mistake on my side. Thank you for your correction,
Manoj. Well, I checked the packaging manual but not the policy before
posting, and the packaging manual obviously doesn't tell where conf files
has to reside, only how they are handled by dpkg.
> Marcus> Am I missing something? What is wrong about:
>
> Yes, Policy. Let me requote the policy manual to you.
>
> ______________________________________________________________________
> 3.3.7. Configuration files
> --------------------------
>
> Any configuration files created or used by your package should reside
> in `/etc'. If there are several you should consider creating a
> subdirectory named after your package.
> _____________________________________________________________________
>
> Do you, then, interpret it differently from how I did? How can
> policy be made more unambiguous?
No, I don't interpret it differently. It is a clear statement that every
conf file should reside in /etc, I'm sorry again. I did a quick check if
policy is followed:
flora$ grep -v /etc /var/lib/dpkg/info/*.conffiles
base-files.conffiles:/root/.bash_profile
base-files.conffiles:/root/.bashrc
devscripts.conffiles:etc/upload.sites
dosemu.conffiles:/var/lib/dosemu/hdimage.first
gravitywars.conffiles:/var/lib/games/gravitywars/hscore.gw
lesstif-bin.conffiles:usr/X11R6/lib/X11/mwm/system.mwmrc
mime-support.conffiles:/var/lib/mime/mime-db
mirrormagic.conffiles:/var/lib/games/mirrormagic/RAY.level
modutils.conffiles:/sbin/request-route
nethack.conffiles:/var/lib/games/nethack/logfile
nethack.conffiles:/var/lib/games/nethack/record
povray-misc.conffiles:etc/povray.ini
rocks-n-diamonds.conffiles:/var/lib/games/rocksndiamonds/ROCKS.levelinfo
thrust.conffiles:/var/lib/games/thrust.highscore
xboing.conffiles:/var/lib/games/xboing.score
xearth.conffiles:/usr/X11R6/lib/X11/app-defaults/XEarth
xemacs20-support.conffiles:
xephem-smotif.conffiles:/usr/X11R6/lib/X11/app-defaults/XEphem
xloadimage.conffiles:etc/X11/Xloadimage
xonix.conffiles:/var/lib/games/xonix.scores
Mmmh. It seems that often files under /var also can be conffiles (if a
default file is provided by the package).
> Marcus> 1) Zero conf files in /usr/lib/<package> An option to fetch
> Marcus> and install the roms via ftp in the postinst and a warning
> Marcus> that one should keep the files if dpkg asks to replace them in
> Marcus> future upgrades.
>
> If they are not conf files, dpkg shall *NOT ASK*. Please read
> the Packaging manual.
Come on, Manoj. I wrote "Zero conf files", because I assumed that they could
be conf files, as you well know. If they would be conf files, dpkg *would*
ask.
This leads to the simple questions why conf files should reside in /etc.
The answer is because they are likely to be subject of modifications, isn't
it? But the ROM images are not subject of modification (only once, when they
are downloaded and installed). So the feature of dpkg (namely conf file
handling), could be exploited:
1) the rom images would reside in the /usr area.
2) they would be removed when the package is purged, but not when it is
removed, because dpkg would know of them.
You are right that policy is clear about the subject, but policy is not
applicable to every situation. We have a special case here and the conf file
handling may be appropriate to "mis"-use here. It is only a suggestion, my 2
cents, my little unhumble opinion, etc.
> manoj
> concerned about how little developers know about our policies as
> spelled out in the policy manual
You can easily find out that I'm developer for not a very long time, and my
packages don't use conf files. Policy is long and complicated and changing
fast, so I only read the sections I need for my packages carefully and skim
about the others.
So please accept my apologies that I did the first paragraph wrong and
please think again about the possibility to make the rom images conf files
(although it is against policy) for the benefit of the side effects
(correct handling by dpkg).
What I would like to know is, if there are technical arguments against this
procedure I don't see.
Thank you,
Marcus
--
"Rhubarb is no Egyptian god." Debian GNU/Linux finger brinkmd@
Marcus Brinkmann http://www.debian.org master.debian.org
Marcus.Brinkmann@ruhr-uni-bochum.de for public PGP Key
http://homepage.ruhr-uni-bochum.de/Marcus.Brinkmann/ PGP Key ID 36E7CD09
--
TO UNSUBSCRIBE FROM THIS MAILING LIST: e-mail the word "unsubscribe" to
debian-devel-request@lists.debian.org .
Trouble? e-mail to templin@bucknell.edu .
Reply to: