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.

Sign up for GitHub

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

Jump to bottom

Instantiate Specfile with a string #248

Open
2 tasks done
danishprakash opened this issue Jul 10, 2023 · 3 comments
Open
2 tasks done

Instantiate Specfile with a string #248

danishprakash opened this issue Jul 10, 2023 · 3 comments
Assignees
@nforro
Labels
area/user-experience Usability issue complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/low This issue impacts only a few users. kind/feature New feature or a request for enhancement. workaround-exists There is an existing workaround that can be used in the meantime of implementing the issue.

Comments

@danishprakash
Copy link

Description

Currently, it's possible to do this via a file path. In my use case, all I'm doing is fetching the specfile for multiple packages via OSC API and then trying to parse them using Specfile. I'm currently creating a temp file and then passing it on to the package.

Is this something that can be supported or have there been any discussions in the past about this that ruled it out?

Benefit

No response

Importance

No response

Workaround

  • There is an existing workaround that can be used until this feature is implemented.

Participation

  • I am willing to submit a pull request for this issue. (Packit team is happy to help!)
@nforro
Copy link
Member

nforro commented Jul 10, 2023

This should definitely be possible, let me think about implementation.

@nforro nforro self-assigned this Jul 10, 2023
@nforro nforro moved this from new to backlog in Packit Kanban Board Jul 10, 2023
@nforro nforro added area/user-experience Usability issue complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/low This issue impacts only a few users. kind/feature New feature or a request for enhancement. workaround-exists There is an existing workaround that can be used in the meantime of implementing the issue. labels Jul 10, 2023
@danishprakash
Copy link
Author

That's great, let me know If I can help with this.

@lachmanfrantisek
Copy link
Member

Still relevant. @danishprakash by any chance, would you be interested in contributing this? (We can definitely help.)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@nforro nforro

Labels
area/user-experience Usability issue complexity/single-task Regular task, should be done within days. gain/high This brings a lot of value to (not strictly a lot of) users. impact/low This issue impacts only a few users. kind/feature New feature or a request for enhancement. workaround-exists There is an existing workaround that can be used in the meantime of implementing the issue.
Projects
Packit Kanban Board
Status: backlog
Milestone
No milestone
Development

No branches or pull requests
3 participants
@nforro @danishprakash @lachmanfrantisek