Re: Default Configuration Issues
On Wed, Sep 1, 2010 at 1:35 AM, Dominique Dumont wrote: > Le mardi 31 août 2010 19:17:17, Dominique Dumont a écrit : >> I can come up with a scheme to upgrade fluxbox config file, but I wonder >> if modification of /home/*/fluxbox/ files is acceptable when upgrading a >> package? > > I've seen in a more recent thread that user files are off-limit... > > I guess that fixing fluxbox user's config files must be triggered manually. The maintainer scripts cannot touch /home, but fluxbox when launched as $user could automatically upgrade that user's configuration. I would suggest that upstream would be the place to add this. -- bye, pabs http://wiki.debian.org/PaulWise -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktima4zb45ofxqqxgwsr5d=upcmljfyzehoh...@mail.gmail.com
Re: Default Configuration Issues
Le mardi 31 août 2010 19:17:17, Dominique Dumont a écrit : > I can come up with a scheme to upgrade fluxbox config file, but I wonder > if modification of /home/*/fluxbox/ files is acceptable when upgrading a > package? I've seen in a more recent thread that user files are off-limit... I guess that fixing fluxbox user's config files must be triggered manually. Dominique -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201008311935.13697.domi.dum...@free.fr
Re: Default Configuration Issues
Le samedi 14 août 2010 14:16:14, Paul Tagliamonte a écrit : > > In general, a change in behavior can be handled gracefully with some > > time for "transitions", so that they users can adapt to that (before > > that becomes the default) and with a conspicuous notice (say, in NEWS). > > Hurmm. This makes perfect sense. Is there anything I can do after the > fact? I've done the damage, and I'd really not like to leave people > with half-working installs of fluxbox when they upgrade. Hmm, I may not have an immediate solution, but this is an interesting use case for configuration upgrade based on config-model [1]. Although in this case we are dealing with config files stored in user's home dir. I can come up with a scheme to upgrade fluxbox config file, but I wonder if modification of /home/*/fluxbox/ files is acceptable when upgrading a package? All the best Dominique [1] http://wiki.debian.org/PackageConfigUpgrade -- http://config-model.wiki.sourceforge.net/ -o- http://search.cpan.org/~ddumont/ http://www.ohloh.net/accounts/ddumont -o- http://ddumont.wordpress.com/ -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/201008311917.17847.domi.dum...@free.fr
Re: Default Configuration Issues
In , Paul Tagliamonte wrote: >fluxboxes (or is that fluxboxii) Definitely not fluxboxii, unless it is a loan word from a language I am entirely unfamiliar with. It is probably fluxboxes (c.f. box -> boxes) but it might also be fluxboxen (c.f. ox -> oxen). -- Boyd Stephen Smith Jr. ,= ,-_-. =. b...@iguanasuicide.net ((_/)o o(\_)) ICQ: 514984 YM/AIM: DaTwinkDaddy `-'(. .)`-' http://iguanasuicide.net/\_/ signature.asc Description: This is a digitally signed message part.
Re: Default Configuration Issues
2010/8/14 Rogério Brito :
> Hi, Paul.
>
> On Aug 13 2010, Paul Tagliamonte wrote:
>> I'm a co-maintainer on the "Fluxbox" package.
>
> I happen to be a user of fluxbox.
Thank you :)
>
> Oh, just one stylistic note about the way that you write things both in
> your text and in your changelogs:
>
>> ( even though they have had regular development since then ).
>
> You seem to put one space after a left parenthesis and one before the
> right parenthesis. The usual rules for typesetting text dictates that
> there should be no such spaces. Therefore, the text above should be
> written as:
>
> (even though they have had regular development since then).
Noted duly. I'll make sure I do this from now on. It's a habit from
how I program.
>
>> The stock ( un-configured ) behavior of Fluxbox was to allow
>> window-dragging with a left-click.
>
> You probably meant window dragging with a left click on the title bar,
> right?
Yes
>
>> Since this was stock before, the old version of the debian keys file
>> does not have the configuration directive ( OnTitlebar Mouse1
>> :StartMoving ) to enable left-click window moving.
>
> OK.
>
>> I found this out early, and patched the global configuration file.
>
> OK.
>
>> Fluxbox, however, copies the file to the ~/.fluxbox folder,
>
> "the file" means the global configuration file?
Yup.
>
>> and uses that without checking for additional directives in the global
>> conf file. Whoops.
>
> This is not clear: you say that "uses that" (the global config file?)
> "without checking for additional directives in the global conf file".
> If it is using the global configuration file, it is honoring the
> settings there, isn't it?
I thought that when I patched the global settings file that fluxbox
would import settings from there, then import settings from the user
local config file. Since the configuration directive is not in the
user local settings for fluxboxes (or is that fluxboxii) of years
past, I thought it would have pulled from the global file and not
caused issues.
I was wrong.
>
> Your description didn't sound precise here.
>
>> This is causing breakage of old installs that are upgrading. What is
>> the "right" way of fixing this?
>
> In general, a change in behavior can be handled gracefully with some
> time for "transitions", so that they users can adapt to that (before
> that becomes the default) and with a conspicuous notice (say, in NEWS).
Hurmm. This makes perfect sense. Is there anything I can do after the
fact? I've done the damage, and I'd really not like to leave people
with half-working installs of fluxbox when they upgrade.
>
>
> Regards,
>
> --
> Rogério Brito : rbr...@{ime.usp.br,gmail.com} : GPG key 1024D/7C2CAEB8
> http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
> DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
>
Thanks,
Paul Tagliamonte
--
#define sizeof(x) rand()
:wq
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive:
http://lists.debian.org/aanlktimikr2k5c81xxj-r2bu0jsf5myg9ewmwelni...@mail.gmail.com
Re: Default Configuration Issues
Hi, Paul.
On Aug 13 2010, Paul Tagliamonte wrote:
> I'm a co-maintainer on the "Fluxbox" package.
I happen to be a user of fluxbox.
Oh, just one stylistic note about the way that you write things both in
your text and in your changelogs:
> ( even though they have had regular development since then ).
You seem to put one space after a left parenthesis and one before the
right parenthesis. The usual rules for typesetting text dictates that
there should be no such spaces. Therefore, the text above should be
written as:
(even though they have had regular development since then).
> The stock ( un-configured ) behavior of Fluxbox was to allow
> window-dragging with a left-click.
You probably meant window dragging with a left click on the title bar,
right?
> Since this was stock before, the old version of the debian keys file
> does not have the configuration directive ( OnTitlebar Mouse1
> :StartMoving ) to enable left-click window moving.
OK.
> I found this out early, and patched the global configuration file.
OK.
> Fluxbox, however, copies the file to the ~/.fluxbox folder,
"the file" means the global configuration file?
> and uses that without checking for additional directives in the global
> conf file. Whoops.
This is not clear: you say that "uses that" (the global config file?)
"without checking for additional directives in the global conf file".
If it is using the global configuration file, it is honoring the
settings there, isn't it?
Your description didn't sound precise here.
> This is causing breakage of old installs that are upgrading. What is
> the "right" way of fixing this?
In general, a change in behavior can be handled gracefully with some
time for "transitions", so that they users can adapt to that (before
that becomes the default) and with a conspicuous notice (say, in NEWS).
Regards,
--
Rogério Brito : rbr...@{ime.usp.br,gmail.com} : GPG key 1024D/7C2CAEB8
http://rb.doesntexist.org : Packages for LaTeX : algorithms.berlios.de
DebianQA: http://qa.debian.org/developer.php?login=rbrito%40ime.usp.br
--
To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/20100814055539.ga2...@ime.usp.br
Default Configuration Issues
Hey Mentors, I'm a co-maintainer on the "Fluxbox" package. I have recently moved to packaging their git head, as their last release was 2008 ( even though they have had regular development since then ). The stock ( un-configured ) behavior of Fluxbox was to allow window-dragging with a left-click. This has been changed for the next release ( and thusly, the git head ). Since this was stock before, the old version of the debian keys file does not have the configuration directive ( OnTitlebar Mouse1 :StartMoving ) to enable left-click window moving. I found this out early, and patched the global configuration file. Fluxbox, however, copies the file to the ~/.fluxbox folder, and uses that without checking for additional directives in the global conf file. Whoops. This is causing breakage of old installs that are upgrading. What is the "right" way of fixing this? -Paul Tagliamonte -- #define sizeof(x) rand() :wq -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org Archive: http://lists.debian.org/aanlktims+5oftjhy71pylyjwnb0xsz1k97p=ecgqo...@mail.gmail.com
