search

rpattabi / diskpacker

Automatically exported from code.google.com/p/diskpacker
0 stars 0 forks source link

Outputs should go in a different folder #11

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago 
As of now (Rivision 22), output files are created at source code directory
(lib). 

Output files should go to a different folder, perhaps a subfolder or
configured by the user.

Original issue reported on code.google.com by ananth.p...@gmail.com on 3 Jun 2008 at 4:13

GoogleCodeExporter commented 9 years ago 
all output files in code directory? this is making me nervous. Please, please 
send
them to a subfolder soon.

Original comment by ananth.p...@gmail.com on 12 Jun 2008 at 4:03

GoogleCodeExporter commented 9 years ago

Original comment by ragunath...@gmail.com on 16 Jun 2008 at 3:26

GoogleCodeExporter commented 9 years ago 
Fixed. Output is created in temporary folder by default. In addition to that the
output files are now organised in a tree structure. See revision 32. An example
output structure:

/tmp/disk_packer_ouput/
    diskpacker_report_linux.txt
    diskpacker_report_windows.txt
    /tmp/disk_packer_ouput/delete_scripts:
        linux
            delete_backup_set_0.sh
        windows
            delete_backup_set_0.bat
    /tmp/disk_packer_ouput/disk_burning_projects:
        brasero
            brasero_BACKUP_0.xml
        infra_recorder
            BACKUP_0.irp

Original comment by ragunath...@gmail.com on 21 Jun 2008 at 6:36

GoogleCodeExporter commented 9 years ago 
On Windows, according to Dir::tmpdir, output is going to
<drive>:\Documents and Settings\<user>\Local Settings\Temp\disk_packer_ouput

It'll be much better if outputs go to a folder around/under lib, or something 
set by
the user.

Original comment by ananth.p...@gmail.com on 24 Jul 2008 at 9:54