Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Migrate to using VirtualCodebase from the latest scancode #101

Closed
steven-esser opened this issue Apr 6, 2018 · 6 comments · Fixed by #167
Closed

Migrate to using VirtualCodebase from the latest scancode #101

steven-esser opened this issue Apr 6, 2018 · 6 comments · Fixed by #167
Assignees
Labels
enhancement GSOC Project/issues to be done during the GSOC Time frame needs design refactoring should have
Milestone

Comments

@steven-esser
Copy link
Contributor

scancode-toolkit can re-create a Codebase object and its Resource (files, dirs) from a scancode json results file.

It will useful to convert DeltaCode to using this VirtualCodebase object as the means of doing all the delta operations. Their natural tree structure makes traversing a scan easier, and a variety of other delta operations become easier to do. We also wont have to maintain as many python Objects as we do now; most of these are replicated in a VirtualCodebase (License, Copyright, etc)

@Pratikrocks
Copy link
Collaborator

@MaJuRG , @johnmhoran I can not get this following line :

scancode-toolkit can re-create a Codebase object and its Resource (files, dirs) from a scancode json results file.

What I know is scancode can generate a json output upon scanning a particular codebase,
using this or similar related commands ::
./scancode -clip --json-pp - samples

So basically I want to know what does CodeBase object and Virtual codebase refers in this context.
Can you please clarify it ,as I would like to solve this issue done

@steven-esser
Copy link
Contributor Author

@Pratikrocks
Copy link
Collaborator

Thanks @MaJuRG for the explanation 😃

@kjuq
Copy link

kjuq commented Mar 26, 2020

@MaJuRG @arnav-mandal1234 Hello. I have 2 questions.

  • Do I have to write a concrete plan on GSoC proposal? In other words, is a specific description (like, "This and this will be replaced by using VirtualCodebase. The returning values should be like this. Arguements are... etc.) needed?
  • Or, are general understanging and strict scheduling important/enough?

Thanks.

@steven-esser
Copy link
Contributor Author

@kvoj the more detailed, the better.

@kjuq
Copy link

kjuq commented Mar 29, 2020

@MaJuRG Okay. Thank you.

@Pratikrocks Pratikrocks linked a pull request Jun 24, 2021 that will close this issue
@Pratikrocks Pratikrocks added the GSOC Project/issues to be done during the GSOC Time frame label Jun 24, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement GSOC Project/issues to be done during the GSOC Time frame needs design refactoring should have
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants