Re: Announcing: dotfuse a project this list may find useful
On Thu, 2011-04-07 at 23:42 +0200, Richard Hartmann wrote: > On Thu, Apr 7, 2011 at 22:40, Dieter Plaetinck wrote: > > > Me too. But I got kinda demotivated after my previous attempts to get it > > going failed. > > Feel free to give it another go, you have my full support. > > Who else is in favour of this? Do we want to hammer out a full > proposal on this list, first? > > Dieter, can you send any and all suggestions, planning and > brainstorming to me/this list so we have it in one place? I'm in agreement here. One of my original intentions in starting this list was that it was a place that in addition to the "big picture" of how to create tools for managing our home directories, we'd be also discussing more "day-to-day" topics as how to best deal with the volatility in certain programs' configuration files. If there's a way we can get lots of leverage with lots of developers at once that would be great. --Ken ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: Announcing: dotfuse a project this list may find useful
On Thu, Apr 7, 2011 at 22:40, Dieter Plaetinck wrote: > Me too. But I got kinda demotivated after my previous attempts to get it > going failed. > Feel free to give it another go, you have my full support. Who else is in favour of this? Do we want to hammer out a full proposal on this list, first? Dieter, can you send any and all suggestions, planning and brainstorming to me/this list so we have it in one place? Thanks, Richard ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: Announcing: dotfuse a project this list may find useful
On Thu, 7 Apr 2011 21:19:42 +0200 Richard Hartmann wrote: > On Thu, Apr 7, 2011 at 18:03, Dieter Plaetinck wrote: > > > I also brought this up on the fd.o xdg lists > > $XDG_CONFIG_HOME/app/config for config > $XDG_CONFIG_HOME/app/state for state > > This does seem to make a lot of sense and if we contact the relevant > ML in bulk, with a well-layed-out proposal and get some devs for > larger projects into it _beforehand_, this should be able to go > somewhere. > > I would _really_ like this. Me too. But I got kinda demotivated after my previous attempts to get it going failed. Feel free to give it another go, you have my full support. Dieter ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: Announcing: dotfuse a project this list may find useful
On Thu, Apr 7, 2011 at 18:03, Dieter Plaetinck wrote: > I also brought this up on the fd.o xdg lists $XDG_CONFIG_HOME/app/config for config $XDG_CONFIG_HOME/app/state for state This does seem to make a lot of sense and if we contact the relevant ML in bulk, with a well-layed-out proposal and get some devs for larger projects into it _beforehand_, this should be able to go somewhere. I would _really_ like this. Richard ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: Announcing: dotfuse a project this list may find useful
On Thu, 7 Apr 2011 17:54:40 +0200 martin f krafft wrote: > also sprach Dieter Plaetinck [2011.04.07.1721 > +0200]: > > well, in my experience, many of the apps who like to modify the > > rc/config files themselves, do it quite frequently. Thinks like > > "last window position" or "last open folder [in the app]" can get > > updated a few to tens of times per day. I wouldn't like to > > reintegrate all that myself manually. > > Then file bugs for those are cache data, not configuration data. ;) > I wish it was so simple. I have actually reported this for some projects, but sometimes I bump into a brick wall and often the software is too complex for me to maintain a fork. example: http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2243 I also brought this up on the fd.o xdg lists: many apps implementing the xdg basedir imho are abusive because they store state in config files, some people agreed with me, others said "But I actually _do_ care about this stuff", so I showed them a compromise by suggesting "automatically saved [by the app] config/state/whateveryouwannacallit" could still be stored in $XDG_CONFIG_HOME (like they do now) but just in a different file (so that I can gitignore it)". That would be a solution that works for everyone. But these folks basically just ignore you if you're not a respected gnome/kde developer. http://permalink.gmane.org/gmane.linux.xdg.devel/10929 Dieter ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: Announcing: dotfuse a project this list may find useful
also sprach Dieter Plaetinck [2011.04.07.1721 +0200]: > well, in my experience, many of the apps who like to modify the > rc/config files themselves, do it quite frequently. Thinks like > "last window position" or "last open folder [in the app]" can get > updated a few to tens of times per day. I wouldn't like to > reintegrate all that myself manually. Then file bugs for those are cache data, not configuration data. ;) -- martin | http://madduck.net/ | http://two.sentenc.es/ anyone who says sunshine brings happiness has never danced in the rain. spamtraps: madduck.bo...@madduck.net digital_signature_gpg.asc Description: Digital signature (see http://martin-krafft.net/gpg/sig-policy/999bbcc4/current) ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
Re: Announcing: dotfuse a project this list may find useful
On Wed, 6 Apr 2011 10:47:13 +0200 martin f krafft wrote: > also sprach Erich Heine [2011.03.13.1710 +0100]: > > I'm not sure how to get around this just yet, other than suggest > > not using this system for configuring programs that modify the rcs > > internally. Although now that I think about it, a read could > > trigger a hook, calling a per config file script which would know > > how to parse the config and possibly decompose it to the > > appropriate templates. > > You could write a diff of the file as written by the programme > against the file as would be generated from the templates. Existence > of a diff would trigger warnings to the user whenever possible to > reintegrate the diff into the templates. I use this system for my > SSH known_hosts management: new hosts are added to a temporary file, > and SSH (wrapped by a zsh function) warns me of its existence, > meaning that I have to integrate new hosts. > well, in my experience, many of the apps who like to modify the rc/config files themselves, do it quite frequently. Thinks like "last window position" or "last open folder [in the app]" can get updated a few to tens of times per day. I wouldn't like to reintegrate all that myself manually. I've been thinking about this problem before (more in the context of manually version controlling everything). I've then pondered things such as "selective ignores" (a vcs could ignore changes to files on a granular level: i.e. not per-file, but by checking if changes match a pattern or not), if git would support this for example, irrelevant changes could then be made not to show up in `git status` or `git diff`, already greatly reducing any manual interventions. I think Eric's idea of "parse the new config and adapt the templates automatically" would be too complex to implement/maintain. The scripts would also be very application-specific. Dieter ___ vcs-home mailing list vcs-home@lists.madduck.net http://lists.madduck.net/listinfo/vcs-home
