2 packages sharing the same config file.
I just adopted xabacus. It conflicts with xmabacus because both try to install the same config file /etc/X11/app-defaults/Abacus. Policy is really strict about this : 11.7.4 Sharing configuration files Packages which specify the same file as `conffile' must be tagged as conflicting with each other. Now at the moment the /etc/X11/app-defaults/Abacus file isn't tagged as 'conffile' (or is it by default ?). Policy also states : 11.7.3 Behavior Configuration file handling must conform to the following behavior: * local changes must be preserved during a package upgrade * configuration files must be preserved when the package is removed, and only deleted when the package is purged. The easy way to achieve this behavior is to make the configuration file a conffile. Any help welcome. BTW xabacus and xmabacus are built from the same source. -- Eric VAN BUGGENHAUT [EMAIL PROTECTED]
2 packages sharing the same config file.
I just adopted xabacus. It conflicts with xmabacus because both try to install the same config file /etc/X11/app-defaults/Abacus. Policy is really strict about this : 11.7.4 Sharing configuration files Packages which specify the same file as `conffile' must be tagged as conflicting with each other. Now at the moment the /etc/X11/app-defaults/Abacus file isn't tagged as 'conffile' (or is it by default ?). Policy also states : 11.7.3 Behavior Configuration file handling must conform to the following behavior: * local changes must be preserved during a package upgrade * configuration files must be preserved when the package is removed, and only deleted when the package is purged. The easy way to achieve this behavior is to make the configuration file a conffile. Any help welcome. BTW xabacus and xmabacus are built from the same source. -- Eric VAN BUGGENHAUT [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
On Fri, May 18, 2001 at 04:22:41AM +0200, [EMAIL PROTECTED] wrote: > I just adopted xabacus. > > It conflicts with xmabacus because both try to install > the same config file /etc/X11/app-defaults/Abacus. > maybe using an abacus-common package which owns that conffile... my question now is, is a file worth of a package on its own?!? -[ Domenico Andreoli, aka cavok --[ http://filibusta.crema.unimi.it/~cavok/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50
Re: 2 packages sharing the same config file.
Domenico Andreoli <[EMAIL PROTECTED]> writes: > maybe using an abacus-common package which owns that conffile... > > my question now is, is a file worth of a package on its own?!? Nope. Why not just leave the packages conflicting until someone with a real need to have both installed stands up? -- Robbe signature.ng Description: PGP signature
Re: 2 packages sharing the same config file.
On Mon, May 21, 2001 at 03:55:42PM +0200, Robert Bihlmeyer wrote: > Domenico Andreoli <[EMAIL PROTECTED]> writes: > > > maybe using an abacus-common package which owns that conffile... > > > > my question now is, is a file worth of a package on its own?!? > > Nope. Why not just leave the packages conflicting until someone with a > real need to have both installed stands up? Well :-) This is the message I got from A. Bunk who handed me the package : >It's your package. One thing you could do when you start working on it is >to remove the conflict between xabacus and xmabacus - there are better >solutions in Debian when two packages share the same file. > >cu >Adrian I'm just looking for the 'better solutions' he mentions but still clueless. Any hint ? -- Eric VAN BUGGENHAUT [EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
On Wed, May 23, 2001 at 03:06:26AM +0200, Eric Van Buggenhaut wrote: > This is the message I got from A. Bunk who handed me the package : > > >It's your package. One thing you could do when you start working on it is > >to remove the conflict between xabacus and xmabacus - there are better > >solutions in Debian when two packages share the same file. > > > >cu > >Adrian > > I'm just looking for the 'better solutions' he mentions but still clueless. > Any > hint ? > I don't know the details here, but can't you just modify the package to use seperate config files for each binary so they no longer conflict? The only other thing I can think of is to put the common files in one package and have the other dependant on it... That might not be a good solution though. Just wanted to throw that out for comment... -- Brett
Re: 2 packages sharing the same config file.
On Wed, May 23, 2001 at 03:06:26AM +0200, Eric Van Buggenhaut wrote:
> I'm just looking for the 'better solutions' he mentions but still clueless.
> Any hint ?
for lib{pam,nss}-ldap i used debconf to share the common data, and just made
the packages use renamed config files.
it makes things easy for the user when (s)he enters the data once and it's
re-used in the other package too. This just leaves you with the situation where
you need to have a way to configure the packages differently too.
--
-< Sami Haahtinen >-
-< 2209 3C53 D0FB 041C F7B1 F908 A9B6 F730 B83D 761C >-
Re: 2 packages sharing the same config file.
Eric Van Buggenhaut wrote: > >It's your package. One thing you could do when you start working on it is > >to remove the conflict between xabacus and xmabacus - there are better > >solutions in Debian when two packages share the same file. > > > >cu > >Adrian > > I'm just looking for the 'better solutions' he mentions but still clueless. > Any > hint ? One possibility would be to not use a conffile, but generate the conffile in your postinst if it does not exist. This still leaves open the question about how you figure out it's safe to remove the conffile. The packages would each have to remove it on purge iff the other package was already purged. -- see shy jo
Re: 2 packages sharing the same config file.
On Sun, May 20, 2001 at 01:42:58AM +0200, Domenico Andreoli wrote: > On Fri, May 18, 2001 at 04:22:41AM +0200, [EMAIL PROTECTED] wrote: > > I just adopted xabacus. > > > > It conflicts with xmabacus because both try to install > > the same config file /etc/X11/app-defaults/Abacus. > > > maybe using an abacus-common package which owns that conffile... > > my question now is, is a file worth of a package on its own?!? Thank you for your answer. Probably not, especially since this file is +- 10 lines long. -- Eric VAN BUGGENHAUT [EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
On Tue, May 22, 2001 at 10:11:48PM -0700, Brett Cundal wrote: > On Wed, May 23, 2001 at 03:06:26AM +0200, Eric Van Buggenhaut wrote: > > This is the message I got from A. Bunk who handed me the package : > > > > >It's your package. One thing you could do when you start working on it is > > >to remove the conflict between xabacus and xmabacus - there are better > > >solutions in Debian when two packages share the same file. > > > > > >cu > > >Adrian > > > > I'm just looking for the 'better solutions' he mentions but still clueless. > > Any > > hint ? > > > > I don't know the details here, but can't you just modify the package to use > seperate config files for each binary so they no longer conflict? > > The only other thing I can think of is to put the common files in one > package and have the other dependant on it... That might not be a good > solution though. > Thank for your comment. Answer to your question is : probably not, the 2 binary files do the same thing. The only difference is that they are built against different libraries (motif/non-motif). The config file just sets thing like the size of the abacus, etc. That's why we use 1 config file for both versions. > Just wanted to throw that out for comment... Any comment is always welcomme :-) -- Eric VAN BUGGENHAUT [EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
On Wed, May 23, 2001 at 09:30:13PM +0300, Sami Haahtinen wrote:
> On Wed, May 23, 2001 at 03:06:26AM +0200, Eric Van Buggenhaut wrote:
> > I'm just looking for the 'better solutions' he mentions but still clueless.
> > Any hint ?
>
> for lib{pam,nss}-ldap i used debconf to share the common data, and just made
> the packages use renamed config files.
>
> it makes things easy for the user when (s)he enters the data once and it's
> re-used in the other package too. This just leaves you with the situation
> where
> you need to have a way to configure the packages differently too.
OK, I'll have a look at your packages, thanks.
--
Eric VAN BUGGENHAUT
[EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
On Wed, May 23, 2001 at 02:49:03PM -0400, Joey Hess wrote: > Eric Van Buggenhaut wrote: > > >It's your package. One thing you could do when you start working on it is > > >to remove the conflict between xabacus and xmabacus - there are better > > >solutions in Debian when two packages share the same file. > > > > > >cu > > >Adrian > > > > I'm just looking for the 'better solutions' he mentions but still clueless. > > Any > > hint ? > > One possibility would be to not use a conffile, but generate the > conffile in your postinst if it does not exist. This still leaves open > the question about how you figure out it's safe to remove the conffile. > The packages would each have to remove it on purge iff the other package > was already purged. It seems the best solution indeed. Is there a way to know if a package has been purged ? dpkg --test-purge ? -- Eric VAN BUGGENHAUT [EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
Eric Van Buggenhaut wrote: > It seems the best solution indeed. Is there a way to know if a package has > been purged ? dpkg --test-purge ? You'll have to play with dpkg -s | grep Status: I guess -- see shy jo
Re: 2 packages sharing the same config file.
On Fri, May 18, 2001 at 04:22:41AM +0200, [EMAIL PROTECTED] wrote: > I just adopted xabacus. > > It conflicts with xmabacus because both try to install > the same config file /etc/X11/app-defaults/Abacus. > maybe using an abacus-common package which owns that conffile... my question now is, is a file worth of a package on its own?!? -[ Domenico Andreoli, aka cavok --[ http://filibusta.crema.unimi.it/~cavok/gpgkey.asc ---[ 3A0F 2F80 F79C 678A 8936 4FEE 0677 9033 A20E BC50 -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
Domenico Andreoli <[EMAIL PROTECTED]> writes: > maybe using an abacus-common package which owns that conffile... > > my question now is, is a file worth of a package on its own?!? Nope. Why not just leave the packages conflicting until someone with a real need to have both installed stands up? -- Robbe signature.ng
Re: 2 packages sharing the same config file.
On Mon, May 21, 2001 at 03:55:42PM +0200, Robert Bihlmeyer wrote: > Domenico Andreoli <[EMAIL PROTECTED]> writes: > > > maybe using an abacus-common package which owns that conffile... > > > > my question now is, is a file worth of a package on its own?!? > > Nope. Why not just leave the packages conflicting until someone with a > real need to have both installed stands up? Well :-) This is the message I got from A. Bunk who handed me the package : >It's your package. One thing you could do when you start working on it is >to remove the conflict between xabacus and xmabacus - there are better >solutions in Debian when two packages share the same file. > >cu >Adrian I'm just looking for the 'better solutions' he mentions but still clueless. Any hint ? -- Eric VAN BUGGENHAUT [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
On Wed, May 23, 2001 at 03:06:26AM +0200, Eric Van Buggenhaut wrote: > This is the message I got from A. Bunk who handed me the package : > > >It's your package. One thing you could do when you start working on it is > >to remove the conflict between xabacus and xmabacus - there are better > >solutions in Debian when two packages share the same file. > > > >cu > >Adrian > > I'm just looking for the 'better solutions' he mentions but still clueless. Any > hint ? > I don't know the details here, but can't you just modify the package to use seperate config files for each binary so they no longer conflict? The only other thing I can think of is to put the common files in one package and have the other dependant on it... That might not be a good solution though. Just wanted to throw that out for comment... -- Brett -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
On Wed, May 23, 2001 at 03:06:26AM +0200, Eric Van Buggenhaut wrote:
> I'm just looking for the 'better solutions' he mentions but still clueless.
> Any hint ?
for lib{pam,nss}-ldap i used debconf to share the common data, and just made
the packages use renamed config files.
it makes things easy for the user when (s)he enters the data once and it's
re-used in the other package too. This just leaves you with the situation where
you need to have a way to configure the packages differently too.
--
-< Sami Haahtinen >-
-< 2209 3C53 D0FB 041C F7B1 F908 A9B6 F730 B83D 761C >-
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
Eric Van Buggenhaut wrote: > >It's your package. One thing you could do when you start working on it is > >to remove the conflict between xabacus and xmabacus - there are better > >solutions in Debian when two packages share the same file. > > > >cu > >Adrian > > I'm just looking for the 'better solutions' he mentions but still clueless. Any > hint ? One possibility would be to not use a conffile, but generate the conffile in your postinst if it does not exist. This still leaves open the question about how you figure out it's safe to remove the conffile. The packages would each have to remove it on purge iff the other package was already purged. -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
On Sun, May 20, 2001 at 01:42:58AM +0200, Domenico Andreoli wrote: > On Fri, May 18, 2001 at 04:22:41AM +0200, [EMAIL PROTECTED] wrote: > > I just adopted xabacus. > > > > It conflicts with xmabacus because both try to install > > the same config file /etc/X11/app-defaults/Abacus. > > > maybe using an abacus-common package which owns that conffile... > > my question now is, is a file worth of a package on its own?!? Thank you for your answer. Probably not, especially since this file is +- 10 lines long. -- Eric VAN BUGGENHAUT [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
On Tue, May 22, 2001 at 10:11:48PM -0700, Brett Cundal wrote: > On Wed, May 23, 2001 at 03:06:26AM +0200, Eric Van Buggenhaut wrote: > > This is the message I got from A. Bunk who handed me the package : > > > > >It's your package. One thing you could do when you start working on it is > > >to remove the conflict between xabacus and xmabacus - there are better > > >solutions in Debian when two packages share the same file. > > > > > >cu > > >Adrian > > > > I'm just looking for the 'better solutions' he mentions but still clueless. Any > > hint ? > > > > I don't know the details here, but can't you just modify the package to use > seperate config files for each binary so they no longer conflict? > > The only other thing I can think of is to put the common files in one > package and have the other dependant on it... That might not be a good > solution though. > Thank for your comment. Answer to your question is : probably not, the 2 binary files do the same thing. The only difference is that they are built against different libraries (motif/non-motif). The config file just sets thing like the size of the abacus, etc. That's why we use 1 config file for both versions. > Just wanted to throw that out for comment... Any comment is always welcomme :-) -- Eric VAN BUGGENHAUT [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
On Wed, May 23, 2001 at 09:30:13PM +0300, Sami Haahtinen wrote:
> On Wed, May 23, 2001 at 03:06:26AM +0200, Eric Van Buggenhaut wrote:
> > I'm just looking for the 'better solutions' he mentions but still clueless.
> > Any hint ?
>
> for lib{pam,nss}-ldap i used debconf to share the common data, and just made
> the packages use renamed config files.
>
> it makes things easy for the user when (s)he enters the data once and it's
> re-used in the other package too. This just leaves you with the situation where
> you need to have a way to configure the packages differently too.
OK, I'll have a look at your packages, thanks.
--
Eric VAN BUGGENHAUT
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
On Wed, May 23, 2001 at 02:49:03PM -0400, Joey Hess wrote: > Eric Van Buggenhaut wrote: > > >It's your package. One thing you could do when you start working on it is > > >to remove the conflict between xabacus and xmabacus - there are better > > >solutions in Debian when two packages share the same file. > > > > > >cu > > >Adrian > > > > I'm just looking for the 'better solutions' he mentions but still clueless. Any > > hint ? > > One possibility would be to not use a conffile, but generate the > conffile in your postinst if it does not exist. This still leaves open > the question about how you figure out it's safe to remove the conffile. > The packages would each have to remove it on purge iff the other package > was already purged. It seems the best solution indeed. Is there a way to know if a package has been purged ? dpkg --test-purge ? -- Eric VAN BUGGENHAUT [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
Re: 2 packages sharing the same config file.
Eric Van Buggenhaut wrote: > It seems the best solution indeed. Is there a way to know if a package has been >purged ? dpkg --test-purge ? You'll have to play with dpkg -s | grep Status: I guess -- see shy jo -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
