Dne 26. 06. 21 v 19:16 Stephen John Smoogen napsal(a):
The process is complicated for multiple reasons:
1. There are a lot of steps to deal with corner cases which have come
up over the years which need to be dealt with.
2. There are some steps to make sure that the package is going to be
maintained versus just dropped and forgotten as a lot of packages have
been.
3. There are a lot of warts/headaches/problems which have been there
but people who have packaged for 20 years no longer see (or in a
Stockholm syndrome feel they NEED to be there.)
In packaging software there are a set of steps you need to ask yourself:
1. Why are you wanting to do this task?
2. What do you expect to get out of this?
3. How committed are you to continually packaging this software?
4. What does this software bring to a complete operating system?
5. Why this operating system?
Shouldn't we have these bullets in the "Join the package collection
maintainers" wiki?
Vít
The first three questions are mostly about personal motivations but it
is something that I see people not answering and then burning
themselves out on finding out how complicated packaging is. Packaging
up software is a long term commitment. It is saying 'I think this
software is useful and will be maintained for years at a time.' If the
software is more of a short term project or you really don't think
that you (or others) want to keep fixing/maintaining it for years..
then the software doesn't really need to be in a distribution but in
some sort of PPA or COPR.
The fourth and fifth are to deal with marketing the software. Just
having it in a distribution isn't going to get it to be used. [In most
distribution early years, they don't take this part seriously and then
end up with hundreds or thousands of ghost packages which end up being
a pain. A distribution then starts adding more 'does anyone need this
really???' type roadblocks which may go into overkill. Or it may be
that putting it in the operating system is going to be a headache the
entire time because the way the operating system deals with the
language set is more work than you care for.
For Fedora/RHEL, programs written in newer languages like Java, Go,
Rust are going to have a lot of rules which seem completely
antithetical to how the language is set up elsewhere. Getting software
written in these is going to need a LOT of extra work which requires
even more dedication. [I am not saying that they shouldn't be done,
but it is more like the 'packaging game' is set to Instadeath/Torment
X mode.
On Sat, 26 Jun 2021 at 06:38, Joan Moreau via devel
<devel@xxxxxxxxxxxxxxxxxxxxxxx> wrote:
Honeslt y , process is so complicated
Now, I am again getting errors about "unaotirzed url"
How to make things happens intesaod of all thisnightmare ?
Thank you
On Wed, 2021-06-23 at 19:58 +0200, Arthur Bols wrote:
On 23/06/2021 19:34, Joan Moreau via devel wrote:
Hello
How can I move forward on this ?
Thank you
Hi Joan,
Could you elaborate please?
As Emmanuel said, you have two options:
a) use a COPR repository and publish instructions on enabling the repo
b) find an existing maintainer to do the heavy lifting and sign on as
a co-maintainer to deal with upstream-related issues. The primary
maintainer will then only have to deal with Fedora-related issues.
Arthur
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
