Closed #2586.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2586#event-11584153608
You are receiving this because you are subscribed to this thread.
Message ID:
___
Rpm-maint mailing list
Rpm
OK, let's do the splitting part ourselves first, via
https://github.com/rpm-software-management/rpm/issues/2873. This PR should then
be migrated to the new repo once it exists. I'll close it here and add a note
to the splitting ticket.
--
Reply to this email directly or view it on GitHub:
http
> I created https://github.com/perlpunk/rpm-perl
> For now it just contains copies of the original perl files.
I'd recommend copying the history too, there's over 20 years of history in
there.
The name of the repo is up to you of course, but just for reference the python
counterpart is named th
> Which license should I use?
Same as rpm package has now, as you copy code. GPL-2.0-or-later according to
the files itself.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2586#issuecomment-1736867275
You are receiving this because you
I created https://github.com/perlpunk/rpm-perl
For now it just contains copies of the original perl files.
Which license should I use?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2586#issuecomment-1736244646
You are receiving this bec
Fedora has [perl-generator](https://src.fedoraproject.org/rpms/perl-generators)
package since 2014.
It contains perl.req, perl.prov and fileattrs based on rpm-4.11.2.
Over the years, there have been some updates in dependency detection and bug
fixes issues reported in Fedora.
We also added som
I do not maintain perl in Fedora. CCing current maintainer, @jplesnik.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2586#issuecomment-1715558411
You are receiving this because you are subscribed to this thread.
Message ID:
cc: @ppisar
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2586#issuecomment-1715005987
You are receiving this because you are subscribed to this thread.
Message ID: ___
Rpm-maint mailing list
We can do that, or just create the repo in this organization to begin with.
Either way, just file the request at
https://github.com/rpm-software-management/org-admin
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2586#issuecomment-1704
@pmatilai thanks.
I would like to start a new package then and work on it together with @stoecker
Should I create a new repo and then request to transfer it to this org?
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2586#issuecomment-17
> But for this first draft I wanted to get your feedback if such a PR is
> welcome or if it should be done in a new package outside of rpm.
We'd actually like the Perl generators to move to a new package outside rpm
entirely. This has been done for eg Python already, but Perl has lingered on
de
See also #2609 for a patch to the existing tool.
--
Reply to this email directly or view it on GitHub:
https://github.com/rpm-software-management/rpm/pull/2586#issuecomment-1675841692
You are receiving this because you are subscribed to this thread.
Message ID: __
## Background
I'm the current maintainer of https://github.com/openSUSE/cpanspec and I
do automatic updates to devel:languages:perl with it.
Perl module versions are decimal versions, and semantically split in triplets.
CPAN --> Normalized, semantical meaning from perl's point of
vi
13 matches
Mail list logo
