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

Specify for single package manager #264

Open
vsoch opened this issue Sep 6, 2022 · 4 comments
Open

Specify for single package manager #264

vsoch opened this issue Sep 6, 2022 · 4 comments
Labels
enhancement New feature or request

Comments

@vsoch
Copy link

vsoch commented Sep 6, 2022

Hi! I'd like to develop for a specific package manager, and I'd rather just be able to target it to run / test instead of running all of them at once. Is there a way to do that? Thanks!

@vsoch vsoch changed the title Produce modules for single package manager Specify for single package manager Sep 6, 2022
@nishakm nishakm added the enhancement New feature or request label Sep 9, 2022
@nishakm
Copy link
Collaborator

nishakm commented Sep 9, 2022

Hi @vsoch! I don't think we can do that right now, but it's definitely something we can integrate. Incidentally, which package manager are you developing for?

@vsoch
Copy link
Author

vsoch commented Sep 9, 2022

I'd like to add spack. I could try to tackle the issue above first though - is that something that would be accepted, and if so, what design preferences do you have?

@nishakm
Copy link
Collaborator

nishakm commented Sep 9, 2022

I'm not sure at this time. Although dependency collection is within scope of the project, we'd like to create a plugin model where external tools can be used. Meanwhile, there seems to be some way of adding an enhancement: https://github.com/opensbom-generator/spdx-sbom-generator#how-to-register-a-new-plugin

@vsoch
Copy link
Author

vsoch commented Sep 25, 2022

hey @nishakm ! Finally started working on this today - yay! A quick question - I'm assuming the model for a Package:

type Module struct {
	Version                 string `json:"Version,omitempty"`
	Name                    string
	Path                    string `json:"Path,omitempty"`
	LocalPath               string `json:"Dir,noempty"`
	Supplier                SupplierContact
	PackageURL              string
	CheckSum                *CheckSum
	PackageHomePage         string
	PackageDownloadLocation string
	LicenseConcluded        string
	LicenseDeclared         string
	CommentsLicense         string
	OtherLicense            []*License
	Copyright               string
	PackageComment          string
	Root                    bool
	Modules                 map[string]*Module
}

The "modules" below it should be dependencies for the module? And for the string should that be the name@version, just the name, or something else?

For spack, it supports environments, but since just having a spack root with packages installed is simpler and more common I'm doing that first.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants