Re: [GNC-dev] [GNC] Gnucash logs

[Bruce Irving via gnucash-devel]

Correct.  I was referring to the data files.  I would have to look hard to find 
the application/program file.I start Gnucash by double-clicking on the desired 
data file and the OS, having been previously associated, opens the application.

Bruce Preach the Gospel wherever you go.  If necessary, use words. 

On Tuesday, May 12, 2020, 7:33:30 AM MDT, Geert Janssens 
 wrote:  
 
 Just to be clear we are talking about the same thing: if you write "GC" you 
are referring to your gnucash data file ? And not to the gnucash application ?

Regards,

Geert

Op zaterdag 9 mei 2020 21:01:49 CEST schreef Bruce Irving via gnucash-devel:
> I like the way it has been, ie: it saves them to the directory where GC is
> located.  Unfortunately, 1 of my installations is leaving the log where the
> link to GC is located.  This is Flathub 3.9 on a Ubuntu derivative. 
> Remarkably, another machine never did that - even before it was upgraded
> (reinstalled) to 3.10.This has worked well for me after I set GC to only
> save them for 7 days.  If it is felt that we need to change to another
> directory, I would be in favor of a daughter of the directory where GC is
> located.  Come to think of it, I would prefer that because then I wouldn't
> have to put GC in a separate directory.
> 
> Bruce Preach the Gospel wherever you go.  If necessary, use words.
> 
> 
> Hi Chris,
> 
> Am 06.05.20 um 06:58 schrieb Chris Good:
> > Does anyone else have some input?
> 
> FYI the related RFE is https://bugs.gnucash.org/show_bug.cgi?id=619119 -
> Can we write log files into seperate directory?
> 
> Regards
> Frank
> 
> 
> --
> 
> Subject: Digest Footer
> 
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> 
> 
> --
> 
> End of gnucash-devel Digest, Vol 206, Issue 10
> **
> 
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel




  
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] [GNC] Gnucash logs

[Geert Janssens]

Just to be clear we are talking about the same thing: if you write "GC" you 
are referring to your gnucash data file ? And not to the gnucash application ?

Regards,

Geert

Op zaterdag 9 mei 2020 21:01:49 CEST schreef Bruce Irving via gnucash-devel:
> I like the way it has been, ie: it saves them to the directory where GC is
> located.  Unfortunately, 1 of my installations is leaving the log where the
> link to GC is located.  This is Flathub 3.9 on a Ubuntu derivative. 
> Remarkably, another machine never did that - even before it was upgraded
> (reinstalled) to 3.10.This has worked well for me after I set GC to only
> save them for 7 days.  If it is felt that we need to change to another
> directory, I would be in favor of a daughter of the directory where GC is
> located.  Come to think of it, I would prefer that because then I wouldn't
> have to put GC in a separate directory.
> 
> Bruce Preach the Gospel wherever you go.  If necessary, use words.
> 
> 
> Hi Chris,
> 
> Am 06.05.20 um 06:58 schrieb Chris Good:
> > Does anyone else have some input?
> 
> FYI the related RFE is https://bugs.gnucash.org/show_bug.cgi?id=619119 -
> Can we write log files into seperate directory?
> 
> Regards
> Frank
> 
> 
> --
> 
> Subject: Digest Footer
> 
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel
> 
> 
> --
> 
> End of gnucash-devel Digest, Vol 206, Issue 10
> **
> 
> ___
> gnucash-devel mailing list
> gnucash-devel@gnucash.org
> https://lists.gnucash.org/mailman/listinfo/gnucash-devel




___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] [GNC] Gnucash logs

[Bruce Irving via gnucash-devel]

I like the way it has been, ie: it saves them to the directory where GC is 
located.  Unfortunately, 1 of my installations is leaving the log where the 
link to GC is located.  This is Flathub 3.9 on a Ubuntu derivative.  
Remarkably, another machine never did that - even before it was upgraded 
(reinstalled) to 3.10.This has worked well for me after I set GC to only save 
them for 7 days.  If it is felt that we need to change to another directory, I 
would be in favor of a daughter of the directory where GC is located.  Come to 
think of it, I would prefer that because then I wouldn't have to put GC in a 
separate directory.

Bruce Preach the Gospel wherever you go.  If necessary, use words. 

  
Hi Chris,

Am 06.05.20 um 06:58 schrieb Chris Good:
> Does anyone else have some input?

FYI the related RFE is https://bugs.gnucash.org/show_bug.cgi?id=619119 -
Can we write log files into seperate directory?

Regards
Frank


--

Subject: Digest Footer

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel


--

End of gnucash-devel Digest, Vol 206, Issue 10
**
  
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] [GNC] Gnucash logs

[Frank H. Ellenberger]

Hi Chris,

Am 06.05.20 um 06:58 schrieb Chris Good:
> Does anyone else have some input?

FYI the related RFE is https://bugs.gnucash.org/show_bug.cgi?id=619119 -
Can we write log files into seperate directory?

Regards
Frank
___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] [GNC] Gnucash logs

[John Ralls]

> On May 5, 2020, at 9:58 PM, Chris Good  wrote:
> 
> 
> 
> Does anyone else have some input?
> 
> If this is going to be ready for GnuCash 4.0 due 20 June 2020, I need to get 
> started ASAP. Otherwise, it 
> 
> won’t be available till 5.0 which is not listed in 
> https://wiki.gnucash.org/wiki/Release_Schedule
> 
> but 4.11 is planned for 2022-12-18.
> 

Feature freeze is the next beta release on 31 May, and you'll need to allow 
some time for your PR to get reviewed.

Regards,
John Ralls

___
gnucash-devel mailing list
gnucash-devel@gnucash.org
https://lists.gnucash.org/mailman/listinfo/gnucash-devel

Re: [GNC-dev] [GNC] Gnucash logs

[Chris Good]

From: Geert Janssens  
Sent: Thursday, 30 April 2020 7:24 PM
To: gnucash-u...@gnucash.org
Cc: Chris Good ; 'David T.' ; 
'David H' 
Subject: Re: [GNC] Gnucash logs

 

Op donderdag 30 april 2020 06:04:10 CEST schreef Chris Good:

> Hi Geert,

> 

> 

> 

> I think options 2-5 are too disruptive and more work than the benefits

> deserve.

> 

> 

> 

> Re option 1,

> 

> I’d prefer to put logs and backups in separate folders. Maybe (going with

> your name) book.dir/backup and book.dir/log. Many people seem to be

> confused about what all these long filenames are when mixed together.

> 

I see I didn't mention this, but that making separate subdirectories for those 
was also intended in my suggestion.

> 

> 

> Also putting the metadata (book.gcm) in book.dir would make if hard to

> notice, so I think it should be in the folder holding book.gnucash (or

> maybe a separate ‘metadata’ subfolder as some people think the metadata

> file is their book).

 

I'm not decided on whether this is a good idea yet. I was throwing it in for 
further consideration. Note that if we do switch to a model with a data file 
and associated directory for other stuff, the metadata file could just be 
called that - metadata.gcm. It's already in the directory with the same name as 
the book. No need to keep that file itself named as the book is.

 

For that matter even the log and backups files could be reduced in file name 
length to only the timestamp. The same applies, the base directory (book.dir) 
uniquely identifies which book they belong to.

 

> 

> Not having all the metadata files for multiple books in the same folder

> means it is more fiddly to share metadata between multiple books by giving

> the books the same name (books in different directories) but there is

> probably nobody doing that anyway (as it is easy to get confused about

> which book is open).

> 

Well, actually you can't. GnuCash has guards in place that make each file name 
in the current metadata directory unique. The filename is just a first 
indication. The actual match between your book and the metadata file is done by 
comparing the root account's GUID in your book with the GUID stored in the 
metadata file.

So if you would have two books named "book.gnucash", you will end up with a 
"books.gcm" and a "books-1.gcm" metadata file. As they are created for diferent 
books, they will both store a unique GUID. When opening either book, gnucash 
will check both metadata files for the one that has your book's GUID stored in 
it.

 

And yes, you could thus circumvent that safety measure by manipulating your 
books to have the same root account GUID. But that's not what the system was 
designed for so we can ignore that hack in this discussion :)

 

Regards,

 

Geert

> 

> 

> Regards,

> 

> Chris Good

> 

> From: Geert Janssens   >

> Sent: Wednesday, 29 April 2020 7:57 PM

> To: gnucash-u...@gnucash.org  

> Cc: Chris Good mailto:goodchri...@gmail.com> >; 
> 'David T.' mailto:sunfis...@yahoo.com> >;

> 'David H' mailto:hell...@gmail.com> > Subject: Re: [GNC] 
> Gnucash logs

> 

> Hi,

> 

> For the file based books (xml and sqlite) there are several approaches:

> 

> 1. Have a book.gnucash and a book.dir side by side, per book you create.

> 

> book.gnucash is your actual data file.

> 

> book.dir is a directory containing extra files related to this data file.

> These include log files, backup files and can potentially be extended to

> hold attachments and possibly book metadata

> 

> Advantages:

> 

> - all data related to one book is stored together in one place. No

> intermingling of (meta)data with other books. Makes it easy to move a book

> to somewhere else

> 

> - as the main book is outside of the the directory it's easy to spot your

> book to open it.

> 

> Disadvantage: per book you will have two items: a file and a directory. At

> the file management level you always have to treat them as one (move them

> together, back them up together,...)

> 

> 2. Have a directory book.gnucash and store all data in there in a structured

> form (logs in their own subdirectory,...). To save a book, you enter the

> book's name and gnucash will create that directory for you. Inside the

> directory your book will now have a generic name (as the directory already

> indicates the unique name) as would log files and backup files. To open a

> book, you select the directory in gnucash and it will open the actual book

> inside of it for you. Backup management could be integrated in gnucash.

> 

> Advantages:

> 

> - like option 1, all data related to a single book is encapsulated closely

> together.

> 

> - only one single element on the file system level to remember: the book.dir

> is your book. Makes it slightly easier to move things around, make backups

> and so on.

> 

> Disadvantage: double-clicking a file to open it in gnucash will no longer

>