Hi Konrad, The sum of the project source code, object and compiled binaries are around 50 MB. Most of that is test files.
When you delete an upload from fossology all the files from the repository and the database will be removed. So if you upload A.tgz, delete it, then reupload A.tgz again, all the files will have to be rescanned (unless they are also part of another upload currently in the repository). Am I understanding your questions correctly? Bob Gobeille On May 15, 2014, at 8:18 AM, Konrad Urbanski <[email protected]> wrote: > Hi Robert, > > Thank you very much for your information. In reference to these information I > have got also some questions: > >> 1. is the memory need for the fossology depending on the largest git blob >> (of several git repositories), or is the combined size of all git blobs >> (pointed to by HEAD in all git repositories) is required? > > I thought about, how much memory the fossology require for the uploaded files > from for example our project source code to the fossology. On the web page it > is described that require 10 x times of the uploaded data. So the question 1 > refers to the project source code that will be uploaded to the fossology not > the fossology itself. > > When it comes for the 2 question, I have another question: when we delete the > source code from the fossology repository (as I understand the result of this > scanned source code will be stored forever in history). What about if we > would like to scan once more time the same source code (previously deleted > from the fossology repository) with the some changes in some files and new > files (it will store the whole source code again, or only the added files and > modified files)? > > We shall be grateful for information. > > Pozdrawiam / Best regards, > > Konrad Urbański, Test Engineer > > Tieto > > > > On 13 May 2014 17:02, Gobeille, Robert <[email protected]> wrote: > Hello Konrad, > > On May 13, 2014, at 5:37 AM, Konrad Urbanski <[email protected]> > wrote: > >> 1. is the memory need for the fossology depending on the largest git blob >> (of several git repositories), or is the combined size of all git blobs >> (pointed to by HEAD in all git repositories) is required? > > There is only one git repository for fossology: > > http://www.fossology.org/projects/fossology/wiki/Git_Download > > However, there is a fossology SPDX module in a second git repository from the > University of Omaha, Nebraska. You can download the source and learn about > it here: > > http://spdxhub.ist.unomaha.edu > > >> 2. when in comes to working fossology, when this program working is it >> stores uploaded data in its own filesystem repository only during the >> scanning operation or after the operation also analysed data is stored >> forever in its own fossology filesystem repository. > > It is stored until you delete the upload. In the fossology main menu you can > chose, Organize > Uploads > Delete Uploaded File. > We would like to add the ability to auto archive/delete uploads but haven’t > gotten to it yet. With this option you could have an upload automatically > archived or deleted after some time period. > > Since you are familiar with git, I’d like to add that fossology also uses > content addressable memory. So if you upload mypkg.src.rpm, change 2 files > and then upload the new version, only those two changed files will take up > storage in the file repository and only those two files will be rescanned. > > Thanks, > Bob Gobeille > FOSSology project leader >
_______________________________________________ fossology mailing list [email protected] http://lists.fossology.org/mailman/listinfo/fossology
