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

package in Debian? #11

Open
lnussbaum opened this issue Jan 6, 2024 · 9 comments
Open

package in Debian? #11

lnussbaum opened this issue Jan 6, 2024 · 9 comments

Comments

@lnussbaum
Copy link

Hi,

Thanks for your great work on parsyncfp2. I used it and have been very impressed!
I'm involved in Debian and would be interested in making it available as a Debian package. But I first wanted to check with you if you have no objections. What do you think?
@hjmangalam
Copy link
Owner

hjmangalam commented Jan 7, 2024 via email

@lnussbaum
Copy link
Author

Hi,

Your COPYRIGHT file says:

   2) All materials or software developed as a consequence of the
      use of this software or software derived from it must duly
      acknowledge such use, in accordance with the usual standards
      of acknowledging credit in academic research.

Which might be read as a requirement, similar to the citation requirement from GNU parallel (see for example the discussion at https://www.reddit.com/r/freesoftware/comments/shqq0r/is_gnu_parallel_in_compliance_with_gplv3/ ).

Would you be open to soften this slightly, to make it clear that this is not an additional requirement on top of the GPL requirements, but rather to request to act following academia standards regarding crediting?

Also, see https://www.gnu.org/licenses/gpl-faq.en.html#RequireCitation

@hjmangalam
Copy link
Owner

hjmangalam commented Jan 11, 2024 via email

@lnussbaum
Copy link
Author

Hi Lucas, Yes, that's a reasonable request. I agree to not placing additional restrictions above what the GPL requires.

Thanks!
Maybe a good way to achieve that would be to drop the COPYRIGHT file entirely (revert to plain GPLv3), and move those requests to the documentation (README and asciidoc) to make it clear that they are not legal requirements. (it would probably also be a better place for the mention of dual licensing).

Also, you are using GPLv3 without the "or later" clause. That's on purpose, right? (That's fine of course)

Thanks again for your work. I haven't looked at the Debian requirements for a long time, but are there recommendations about documentation format? Just if you know offhand - I can google for it if not.

Not really. I am planning to build the doc using asciidoc. I should provide a manpage, but I'm not sure yet how I will address that.

@hjmangalam
Copy link
Owner

hjmangalam commented Jan 11, 2024 via email

@hjmangalam
Copy link
Owner

hjmangalam commented Jan 25, 2024 via email

@lnussbaum
Copy link
Author

Hi,

An update on this:

I uploaded the package to Debian. It will now go through review before it is accepted, which can take a few weeks.
You can look at my packaging in https://salsa.debian.org/debian/parsyncfp2/ (everything is in the debian dir). Possibly interesting things are:

Thanks a lot for your work on parsyncfp2 !

@lnussbaum
Copy link
Author

lnussbaum commented Apr 24, 2024 •
edited
Loading

Hi,
Again an update: parsyncfp2 has been accepted in Debian, and migrated to Debian "testing", so it will be in the next Debian stable release. A dashboard to view the status of the package in Debian is https://tracker.debian.org/pkg/parsyncfp2

@hjmangalam
Copy link
Owner

hjmangalam commented Apr 24, 2024 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@lnussbaum @hjmangalam