Re: Databases and purging
On Wed, Apr 10, 2002 at 08:58:41AM -0600, Gunnar Wolf wrote: > When purging a package that created a database when it was set up, should > I also destroy the database, or is it considered as users' data? i think: dpkg --purge package AFAIK, only remove global configuration files, but not databases of the user. your question its similar to: dpkg --purge bash, remove .bash_profile in the user home directory? oviously not (IMHO) -- Juan Alvarez Fluid Signal S.A. mailto:[EMAIL PROTECTED]http://www.fluidsignal.com/ Key fingerprint: 15C4 0986 A174 862A B607 8EEA 934F 8649 07E2 EA40 msg05950/pgp0.pgp Description: PGP signature
Re: Databases and purging
On Wed, Apr 10, 2002 at 01:19:43PM -0400, Matt Zimmerman wrote: > On Wed, Apr 10, 2002 at 10:32:19AM -0500, Juan Alvarez wrote: > > > your question its similar to: > > > > dpkg --purge bash, > > > > remove .bash_profile in the user home directory? oviously not (IMHO) > > This is not a similar situation, as .bash_profile is not created by the > package installation process. In this case, the database is created by the > maintainer scripts. Generally, this kind of thing should be cleaned up when > the package is purged, but since sometimes this data is valuable, some > packages ask before removing. I think this its a best interpretation than my interpretation. -- Juan Alvarez Fluid Signal S.A. mailto:[EMAIL PROTECTED]http://www.fluidsignal.com/ Key fingerprint: 15C4 0986 A174 862A B607 8EEA 934F 8649 07E2 EA40 msg05958/pgp0.pgp Description: PGP signature
Re: Databases and purging
On Wed, Apr 10, 2002 at 08:58:41AM -0600, Gunnar Wolf wrote: > When purging a package that created a database when it was set up, should > I also destroy the database, or is it considered as users' data? i think: dpkg --purge package AFAIK, only remove global configuration files, but not databases of the user. your question its similar to: dpkg --purge bash, remove .bash_profile in the user home directory? oviously not (IMHO) -- Juan Alvarez Fluid Signal S.A. mailto:[EMAIL PROTECTED]http://www.fluidsignal.com/ Key fingerprint: 15C4 0986 A174 862A B607 8EEA 934F 8649 07E2 EA40 pgpqcC3UtPHJb.pgp Description: PGP signature
Re: Databases and purging
On Wed, Apr 10, 2002 at 01:19:43PM -0400, Matt Zimmerman wrote: > On Wed, Apr 10, 2002 at 10:32:19AM -0500, Juan Alvarez wrote: > > > your question its similar to: > > > > dpkg --purge bash, > > > > remove .bash_profile in the user home directory? oviously not (IMHO) > > This is not a similar situation, as .bash_profile is not created by the > package installation process. In this case, the database is created by the > maintainer scripts. Generally, this kind of thing should be cleaned up when > the package is purged, but since sometimes this data is valuable, some > packages ask before removing. I think this its a best interpretation than my interpretation. -- Juan Alvarez Fluid Signal S.A. mailto:[EMAIL PROTECTED]http://www.fluidsignal.com/ Key fingerprint: 15C4 0986 A174 862A B607 8EEA 934F 8649 07E2 EA40 pgpexhFL9ZHJc.pgp Description: PGP signature
Minimalistic upstream java binary release
I want to package some java library, but the binary release of the upstream is a minimalistic JAR with the copyrigth information. The software has a DFSG copyrigth, but only in the source code, this things implies that my *orig.tar.gz should be the source release (and not the binary release), and compile against all architectures that source althoug the binary release run in every architectures so it doesnt need to recompile? -- Juan Alvarez, Fluidsignal Group S.A. Key fingerprint: 5F35 45B2 34BF 40E7 3AA9 98CE 6E92 E08B 1DDF 6D3C
Re: Minimalistic upstream java binary release
>>>>> "Juan" == Juan Alvarez <[EMAIL PROTECTED]> writes: Juan> I want to package some java library, but the binary release Juan> of the upstream is a minimalistic JAR with the copyrigth Juan> information. Sorry, the binary release of the upstream is a minimalistic jar, ready to production, and dont have the copyrigth. The copyright is only in the upstream binary release. Juan> The software has a DFSG copyrigth, but only in the source Juan> code, this things implies that my *orig.tar.gz should be the Juan> source release (and not the binary release), and compile Juan> against all architectures that source althoug the binary Juan> release run in every architectures so it doesnt need to Juan> recompile? -- Juan Alvarez, Fluidsignal Group S.A. Key fingerprint: 5F35 45B2 34BF 40E7 3AA9 98CE 6E92 E08B 1DDF 6D3C
