Hi Michael, The upload menu includes: >From File >From Server >From URL >From Version Control System
I would propose "From Server" be changed to "From Directory" or "From Directory Tree" which I think is more aligned to the semantics of "From File" . I would also add a checkbox for "Include Subdirectories" and an option for "Include Hidden Files/Subdirectories" which would include or exclude entities starting with a dot (.) Ideally I would also add a filter much like the URL upload has, which would enable me to filter out build artifacts (e.g. .o), or unwanted directory patterns (e.g. where build artifacts get stuffed) Thanks for asking . :) dvb From: Jaeger, Michael C. [mailto:michael.c.jae...@siemens.com] Sent: Wednesday, November 02, 2016 2:45 PM To: David Van Beveren; fossology@lists.fossology.org Subject: RE: [FOSSology] fossology reading from a repo (collection of git repositiries) [followup] Hi, so it works for you? .... What do you propose to have as name or title instead like "Upload from server ..."? Kind regards, Michael From: fossology-boun...@lists.fossology.org<mailto:fossology-boun...@lists.fossology.org> [mailto:fossology-boun...@lists.fossology.org] On Behalf Of David Van Beveren Sent: Mittwoch, 2. November 2016 22:16 To: fossology@lists.fossology.org<mailto:fossology@lists.fossology.org> Subject: Re: [FOSSology] fossology reading from a repo (collection of git repositiries) [followup] We discovered the "Server" upload option actually means fossology and the code are local to the same machine. (Server is not a great designation). Since this is our use case (and source and build are separate), we decided to just point at the source top of tree and upload from there. This makes the need for pulling a repo a non-issue for us. From: fossology-boun...@lists.fossology.org<mailto:fossology-boun...@lists.fossology.org> [mailto:fossology-boun...@lists.fossology.org] On Behalf Of David Van Beveren Sent: Thursday, October 06, 2016 5:20 PM To: fossology@lists.fossology.org<mailto:fossology@lists.fossology.org> Subject: [FOSSology] fossology reading from a repo (collection of git repositiries) I am interested in extending fossology to load a large source file tree via the 'repo' command. Here is a blurb on repo from source.android.com: (there Is no Linux manpage): Repo is a repository management tool that we built on top of Git. Repo unifies the many Git repositories when necessary, does the uploads to Android's revision control system<https://android-review.googlesource.com/>, and automates parts of the Android development workflow. Repo is not meant to replace Git, only to make it easier to work with Git in the context of Android. The repo command is an executable Python script that you can put anywhere in your path. In working with the Android source files, you can use Repo for across-network operations. For example, with a single Repo command you can download files from multiple repositories into your local working directory. I am presuming nobody has done this yet. I'm also presuming that this is not general enough for upstreaming, since repo is mainly an android workflow thing. (though my team does not use it on just android projects). If anyone has experience adding a new uploading mechanism, or wants to give me a good starting point, I am all ears. ________________________________ This email message is for the sole use of the intended recipient(s) and may contain confidential information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message. ________________________________
_______________________________________________ fossology mailing list fossology@lists.fossology.org https://lists.fossology.org/mailman/listinfo/fossology
