Re: [Bobs-devel] excludes and link files

[Rene R. <re...@gr...>]

On Sun, 2002-09-29 at 20:35, Joe zacky wrote:
> If you mean that a list of packages and files to exclude within each 
> package are distributed with BOBS, then I'd say there are too many 
> applications out there to even try to attempt to cover a small portion 
> of them. But, if you mean to provide a page where the admin could create 
> a package and select the exclude files for that package, then yeah, that 
> sounds good, especially if the admin could pick the exclude files from a 
> tree view.
> 
> Excluding files from backups is a hassle for the admin with just about 
> any type of backup system.
> 

I see your point about too many programs.
I hadn't even considered using trees as a way to select them, very good
idea.

My real problem is that some files are really tricky to get right
because they use weird characters. And there is the trick of
understanding how rsync excludes files.

What bothers me about having admins do selecting the files is that they
mostly select the same files. It would a cool thing to have an online
update function which could pass new files to a database and download
other from it (dreaming here...).
That would seem like a good aim to me. Not to be implemented at once,
but to be considered when making it.

I think it would be quite a challenge to design a useful editor for
rsync exclude files. That is, an editor which allows new patterns to be
created, not selecting them from a list.
Wheee.. I love challenges ;-)

In other news:
I've begun moving the last (I think) templates out of the source files.
Once that is done I'll either start with link files or do some more code
clean ups.
As always, please let me know if there is any code you'd like to see
comments on. Then I'll clean it up and add comments.

-Rene



> Rene Rask wrote:
> 
> >I've been pondering how to solve the issues with link files and exludes.
> >
> >It seems to me that it would make sense to make this package based. A
> >package could be a software program.
> >Examples:
> >Netatalk makes some files which are needed for proper operation. They
> >could be in a package which the admin ticks as active. Then those files
> >are not included when making a backup.
> >Likewise Maya has some files which in most cases are not wanted.
> >
> >The problem with having admins make those lists by themselves is that
> >some filename are really tricky to get right (check the current exlude
> >list for an example).
> >
> >Making packages would make it easier to maintain and update the lists.
> >This ofcourse is another admin page that needs doing.
> >
> >I'll start looking into it.
> >
> >Please let me know if you have any thoughts on this.
> >
> >-Rene
> >
> >
> >
> >-------------------------------------------------------
> >This sf.net email is sponsored by:ThinkGeek
> >Welcome to geek heaven.
> >http://thinkgeek.com/sf
> >_______________________________________________
> >Bobs-devel mailing list
> >Bob...@li...
> >https://lists.sourceforge.net/lists/listinfo/bobs-devel
> >
> >  
> >
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> Bobs-devel mailing list
> Bob...@li...
> https://lists.sourceforge.net/lists/listinfo/bobs-devel