Upcoming pakfire.cgi changes.

Upcoming pakfire.cgi changes.

[Stephen Cuka]

Hello,

In reference to the community post:

https://community.ipfire.org/t/core-192-unexpected-upgrade/13760

I'm going to be submitting a set of patches for changes to pakfire.cgi 
to fix some problems, do some cleanup, and hopefully improve the overall 
consistency and appearance of the page.

I wanted to give advance notice of this so that when the patches start 
coming through you'll be aware of what I'm up to.

Below is the list of changes that I'm planning to make.

Let me know of questions, comments or concerns.

Regards,

Stephen

==========

pakfire.cgi patches


1.  Add new translation 'pakfire upgrade' to replace 'upgrade'. The 
'upgrade' tr is only used in pakfire.cgi and this will move the tr into 
the pakfire translation block.

2.  Add new translation 'pakfire install' to replace 'install'. The 
'install' tr is only used in pakfire.cgi and this will move the tr into 
the pakfire translation block.

3.  Add translation 'pakfire updates' to en.pl and it.pl.  It already 
exists in the other languages.  The 'available updates' tr used in 
pakfire.cgi will be changed to 'pakfire updates' which will be in the 
pakfire translation block.

4.  Add translation 'pakfire refresh list'.  pakfire.cgi currently uses 
'calamaris refresh list'.

5.  Add translations 'pakfire resolvedeps wait', 'pakfire dependencies 
found' and 'pakfire no dependencies found' to use on install and remove 
confirmation pages.

6.  Add new translations 'pakfire confirm updates' and 'pakfire 
updating' for new upgrade confirmation page.

7.  Update pakfire.cgi to use 'pakfire upgrade', 'pakfire install', 
'pakfire updates' and 'pakfire refresh list' instead of 'upgrade', 
'install', 'available updates' and 'calamaris refresh list'.

8.  Update pakfire.cgi to convert icons to buttons on the main and 
confirmation pages.  Disable Install, Remove and Upgrade buttons if 
nothing to do.

9.  Update pakfire.cgi to add confirmation page for upgrades.  The 
confirmation page will do a 'pakfire update' to ensure that the local 
pakfire database is current and then display updates to be made and 
request confirmation.  The box title will be 'pakfire upgrade'.

10.  Update pakfire.cgi to change box titles for install and remove 
confirmation pages from 'request' to 'pakfire install' and 'remove'.

11.  Update pakfire.cgi to change 'abort' on confirmation screens to 
'cancel'.

12.  Update pakfire.cgi install and remove confirmation pages. Display 
'pakfire resolve wait' while 'pakfire resolvedeps' is running.  Only 
display 'Need to install...' lines from 'pakfire resolvedeps' output.  
Remove spaces between resolvedeps output lines to tighten up the 
output.  Display "Dependancies found:' before list of dependancies or 
'No dependancies found.' if none found.  The 'Checking

13.  Update pakfire.cgi to change 'uninstall' to 'remove' on 
confirmation page.  The main page uses 'remove' for the minus sign, but 
the confirmation page uses 'uninstall'.

14.  Update pakfire.cgi to adjust some spacing and alignment.

15.  Add missing translations for the cases where the translations are 
English=>English instead of English=>Language.

16.  Clean up
         Delete 'upgrade' tr.  It is now unused.
         Delete 'available updates' tr.  It is now unused.
         Delete 'abort' tr.  It is now unused.
         Delete 'request' tr.  It is now unused.
         Delete 'uninstall' tr.  It is now unused.
         Delete 'pakfire possible dependancy' tr.  It is now unused.
         Delete 'pakfire core update auto' tr.  It is not used.
         Delete 'pakfire health check' tr.  It is not used.
         Delete 'pakfire update daily' tr.  It is not used.


Note on translations:

I am doing translations with multiple web based translation utilities.  
Where the results don't match between the utilities, I look for other 
similar translations in the applicable *language*.pl file and pick the 
one that seems to be most in context or consistent.

Where titles and button text have multiple words.  I capitalize the 
words.  For example 'Available updates:' becomes 'Available Updates:' 
and 'Liste aktualisieren' becomes 'Liste Aktualisieren'.

==========

Re: Upcoming pakfire.cgi changes.

[Michael Tremer]

Hello,

Thanks for taking this conversation to here. Let’s also keep it here...

> On 23 Mar 2025, at 10:48, Stephen Cuka <stephen@firemypi.org> wrote:
> 
> Hello,
> 
> In reference to the community post:
> 
> https://community.ipfire.org/t/core-192-unexpected-upgrade/13760
> 
> I'm going to be submitting a set of patches for changes to pakfire.cgi to fix some problems, do some cleanup, and hopefully improve the overall consistency and appearance of the page.
> 
> I wanted to give advance notice of this so that when the patches start coming through you'll be aware of what I'm up to.

*Received*

> Below is the list of changes that I'm planning to make.
> 
> Let me know of questions, comments or concerns.
> 
> Regards,
> 
> Stephen
> 
> ==========
> 
> pakfire.cgi patches
> 
> 
> 1.  Add new translation 'pakfire upgrade' to replace 'upgrade'. The 'upgrade' tr is only used in pakfire.cgi and this will move the tr into the pakfire translation block.
> 
> 2.  Add new translation 'pakfire install' to replace 'install'. The 'install' tr is only used in pakfire.cgi and this will move the tr into the pakfire translation block.
> 
> 3.  Add translation 'pakfire updates' to en.pl and it.pl.  It already exists in the other languages.  The 'available updates' tr used in pakfire.cgi will be changed to 'pakfire updates' which will be in the pakfire translation block.
> 
> 4.  Add translation 'pakfire refresh list'.  pakfire.cgi currently uses 'calamaris refresh list'.
> 
> 5.  Add translations 'pakfire resolvedeps wait', 'pakfire dependencies found' and 'pakfire no dependencies found' to use on install and remove confirmation pages.
> 
> 6.  Add new translations 'pakfire confirm updates' and 'pakfire updating' for new upgrade confirmation page.
> 
> 7.  Update pakfire.cgi to use 'pakfire upgrade', 'pakfire install', 'pakfire updates' and 'pakfire refresh list' instead of 'upgrade', 'install', 'available updates' and 'calamaris refresh list'.

The translation issues seem to be a much bigger problem than I thought.

> 8.  Update pakfire.cgi to convert icons to buttons on the main and confirmation pages.  Disable Install, Remove and Upgrade buttons if nothing to do.

Hmm, I think this could become a bit confusing, because even though there might not be anything to do right now, a greyed-out button will let the user know where to go whenever there is something to do.

I am also concerned about potential layout breakages if there are so many changes. The entire web UI is incredibly based on tables and removing a cell somewhere might either mess up the layout or you will need to add a lot of code for simple things. I would rather look at investing this time to replace the web UI as a whole.

> 9.  Update pakfire.cgi to add confirmation page for upgrades.  The confirmation page will do a 'pakfire update' to ensure that the local pakfire database is current and then display updates to be made and request confirmation.  The box title will be 'pakfire upgrade'.

Agreed.

> 10.  Update pakfire.cgi to change box titles for install and remove confirmation pages from 'request' to 'pakfire install' and 'remove'.
> 
> 11.  Update pakfire.cgi to change 'abort' on confirmation screens to 'cancel'.
> 
> 12.  Update pakfire.cgi install and remove confirmation pages. Display 'pakfire resolve wait' while 'pakfire resolvedeps' is running.  Only display 'Need to install...' lines from 'pakfire resolvedeps' output.  Remove spaces between resolvedeps output lines to tighten up the output.  Display "Dependancies found:' before list of dependancies or 'No dependancies found.' if none found.  The 'Checking
> 
> 13.  Update pakfire.cgi to change 'uninstall' to 'remove' on confirmation page.  The main page uses 'remove' for the minus sign, but the confirmation page uses 'uninstall'.

I never know which one would be the best term. SuSE is even using “erase”. I think remove makes the most sense and is also visually different from “install” - unlike “uninstall”.

> 14.  Update pakfire.cgi to adjust some spacing and alignment.
> 
> 15.  Add missing translations for the cases where the translations are English=>English instead of English=>Language.

Yeah, this is a difficult topic. In many languages there are native words for things, but everyone is using the English term as it is much easier and to the point. So in German you would still use “Updates” although there is a word like “Aktualisierungen”. So be careful with Google translate :)

> 16.  Clean up
>         Delete 'upgrade' tr.  It is now unused.
>         Delete 'available updates' tr.  It is now unused.
>         Delete 'abort' tr.  It is now unused.
>         Delete 'request' tr.  It is now unused.
>         Delete 'uninstall' tr.  It is now unused.
>         Delete 'pakfire possible dependancy' tr.  It is now unused.
>         Delete 'pakfire core update auto' tr.  It is not used.
>         Delete 'pakfire health check' tr.  It is not used.
>         Delete 'pakfire update daily' tr.  It is not used.

Agreed. You know about “./make.sh lang”?

> Note on translations:
> 
> I am doing translations with multiple web based translation utilities.  Where the results don't match between the utilities, I look for other similar translations in the applicable *language*.pl file and pick the one that seems to be most in context or consistent.

I think this is a good start. We have people on the team who can help with German, Dutch, maybe a bit of French. There are some Italian people on the forum which can help. For the rest, I would consider those translations abandoned and I think it is fine to just do nothing here and the software will automatically put the English version which at least is correct.

> Where titles and button text have multiple words.  I capitalize the words.  For example 'Available updates:' becomes 'Available Updates:' and 'Liste aktualisieren' becomes 'Liste Aktualisieren'.

Yes, I like the words being capitalised in English. It looks a bit wrong to me in German, because only nouns are capitalised. Not sure how people feel about other languages.

Best,
-Michael

> 
> ==========
> 
> 
> 
> 
> 
> 

Re: Upcoming pakfire.cgi changes.

[Stephen Cuka]

Hello,

On 3/23/25 06:32, Michael Tremer wrote:
> Hello,
>
> Thanks for taking this conversation to here. Let’s also keep it here...
>
>> On 23 Mar 2025, at 10:48, Stephen Cuka <stephen@firemypi.org> wrote:
>>
>> Hello,
>>
>> In reference to the community post:
>>
>> https://community.ipfire.org/t/core-192-unexpected-upgrade/13760
>>
>> I'm going to be submitting a set of patches for changes to pakfire.cgi to fix some problems, do some cleanup, and hopefully improve the overall consistency and appearance of the page.
>>
>> I wanted to give advance notice of this so that when the patches start coming through you'll be aware of what I'm up to.
> *Received*
>
>> Below is the list of changes that I'm planning to make.
>>
>> Let me know of questions, comments or concerns.
>>
>> Regards,
>>
>> Stephen
>>
>> ==========
>>
>> pakfire.cgi patches
>>
>>
>> 1.  Add new translation 'pakfire upgrade' to replace 'upgrade'. The 'upgrade' tr is only used in pakfire.cgi and this will move the tr into the pakfire translation block.
>>
>> 2.  Add new translation 'pakfire install' to replace 'install'. The 'install' tr is only used in pakfire.cgi and this will move the tr into the pakfire translation block.
>>
>> 3.  Add translation 'pakfire updates' to en.pl and it.pl.  It already exists in the other languages.  The 'available updates' tr used in pakfire.cgi will be changed to 'pakfire updates' which will be in the pakfire translation block.
>>
>> 4.  Add translation 'pakfire refresh list'.  pakfire.cgi currently uses 'calamaris refresh list'.
>>
>> 5.  Add translations 'pakfire resolvedeps wait', 'pakfire dependencies found' and 'pakfire no dependencies found' to use on install and remove confirmation pages.
>>
>> 6.  Add new translations 'pakfire confirm updates' and 'pakfire updating' for new upgrade confirmation page.
>>
>> 7.  Update pakfire.cgi to use 'pakfire upgrade', 'pakfire install', 'pakfire updates' and 'pakfire refresh list' instead of 'upgrade', 'install', 'available updates' and 'calamaris refresh list'.
> The translation issues seem to be a much bigger problem than I thought.
>
>> 8.  Update pakfire.cgi to convert icons to buttons on the main and confirmation pages.  Disable Install, Remove and Upgrade buttons if nothing to do.
> Hmm, I think this could become a bit confusing, because even though there might not be anything to do right now, a greyed-out button will let the user know where to go whenever there is something to do.
>
> I am also concerned about potential layout breakages if there are so many changes. The entire web UI is incredibly based on tables and removing a cell somewhere might either mess up the layout or you will need to add a lot of code for simple things. I would rather look at investing this time to replace the web UI as a whole.
>
>> 9.  Update pakfire.cgi to add confirmation page for upgrades.  The confirmation page will do a 'pakfire update' to ensure that the local pakfire database is current and then display updates to be made and request confirmation.  The box title will be 'pakfire upgrade'.
The buttons will still be there but greyed out, so no layout changes.  
The Install and Remove buttons will be activated by the onchange 
<select> event so when the user selects an add-on the button activates 
and the user gets kind of a "Click here next!" indication.  The Upgrade 
button will be active if there is anything to update displayed in the 
'Available Updates:' box.  In either case, the confirmation pages won't 
be displayed if there is nothing to do.
> Agreed.
>
>> 10.  Update pakfire.cgi to change box titles for install and remove confirmation pages from 'request' to 'pakfire install' and 'remove'.
>>
>> 11.  Update pakfire.cgi to change 'abort' on confirmation screens to 'cancel'.
>>
>> 12.  Update pakfire.cgi install and remove confirmation pages. Display 'pakfire resolve wait' while 'pakfire resolvedeps' is running.  Only display 'Need to install...' lines from 'pakfire resolvedeps' output.  Remove spaces between resolvedeps output lines to tighten up the output.  Display "Dependancies found:' before list of dependancies or 'No dependancies found.' if none found.  The 'Checking
>>
>> 13.  Update pakfire.cgi to change 'uninstall' to 'remove' on confirmation page.  The main page uses 'remove' for the minus sign, but the confirmation page uses 'uninstall'.
> I never know which one would be the best term. SuSE is even using “erase”. I think remove makes the most sense and is also visually different from “install” - unlike “uninstall”.
>
>> 14.  Update pakfire.cgi to adjust some spacing and alignment.
>>
>> 15.  Add missing translations for the cases where the translations are English=>English instead of English=>Language.
> Yeah, this is a difficult topic. In many languages there are native words for things, but everyone is using the English term as it is much easier and to the point. So in German you would still use “Updates” although there is a word like “Aktualisierungen”. So be careful with Google translate :)
>
>> 16.  Clean up
>>          Delete 'upgrade' tr.  It is now unused.
>>          Delete 'available updates' tr.  It is now unused.
>>          Delete 'abort' tr.  It is now unused.
>>          Delete 'request' tr.  It is now unused.
>>          Delete 'uninstall' tr.  It is now unused.
>>          Delete 'pakfire possible dependancy' tr.  It is now unused.
>>          Delete 'pakfire core update auto' tr.  It is not used.
>>          Delete 'pakfire health check' tr.  It is not used.
>>          Delete 'pakfire update daily' tr.  It is not used.
> Agreed. You know about “./make.sh lang”?
Nope, did not know that.

I'll run that before sending patches with tr changes so that 
issues/missings get updated.
>> Note on translations:
>>
>> I am doing translations with multiple web based translation utilities.  Where the results don't match between the utilities, I look for other similar translations in the applicable *language*.pl file and pick the one that seems to be most in context or consistent.
> I think this is a good start. We have people on the team who can help with German, Dutch, maybe a bit of French. There are some Italian people on the forum which can help. For the rest, I would consider those translations abandoned and I think it is fine to just do nothing here and the software will automatically put the English version which at least is correct.
>
>> Where titles and button text have multiple words.  I capitalize the words.  For example 'Available updates:' becomes 'Available Updates:' and 'Liste aktualisieren' becomes 'Liste Aktualisieren'.
> Yes, I like the words being capitalised in English. It looks a bit wrong to me in German, because only nouns are capitalised. Not sure how people feel about other languages.
I'll change the German back to "Liste aktualisieren".  Hopefully there 
will be enough language review from the team to keep me from doing 
anything incredibly weird.  :)
>
> Best,
> -Michael
>
>> ==========
>>
>>
>>
>>
>>
>>
Regards,
Stephen

Re: Upcoming pakfire.cgi changes.

[Michael Tremer]

Hello Stephen,

> On 23 Mar 2025, at 19:11, Stephen Cuka <stephen@firemypi.org> wrote:
> 
> Hello,
> 
> On 3/23/25 06:32, Michael Tremer wrote:
>> Hello,
>> 
>> Thanks for taking this conversation to here. Let’s also keep it here...
>> 
>>> On 23 Mar 2025, at 10:48, Stephen Cuka <stephen@firemypi.org> wrote:
>>> 
>>> Hello,
>>> 
>>> In reference to the community post:
>>> 
>>> https://community.ipfire.org/t/core-192-unexpected-upgrade/13760
>>> 
>>> I'm going to be submitting a set of patches for changes to pakfire.cgi to fix some problems, do some cleanup, and hopefully improve the overall consistency and appearance of the page.
>>> 
>>> I wanted to give advance notice of this so that when the patches start coming through you'll be aware of what I'm up to.
>> *Received*
>> 
>>> Below is the list of changes that I'm planning to make.
>>> 
>>> Let me know of questions, comments or concerns.
>>> 
>>> Regards,
>>> 
>>> Stephen
>>> 
>>> ==========
>>> 
>>> pakfire.cgi patches
>>> 
>>> 
>>> 1.  Add new translation 'pakfire upgrade' to replace 'upgrade'. The 'upgrade' tr is only used in pakfire.cgi and this will move the tr into the pakfire translation block.
>>> 
>>> 2.  Add new translation 'pakfire install' to replace 'install'. The 'install' tr is only used in pakfire.cgi and this will move the tr into the pakfire translation block.
>>> 
>>> 3.  Add translation 'pakfire updates' to en.pl and it.pl.  It already exists in the other languages.  The 'available updates' tr used in pakfire.cgi will be changed to 'pakfire updates' which will be in the pakfire translation block.
>>> 
>>> 4.  Add translation 'pakfire refresh list'.  pakfire.cgi currently uses 'calamaris refresh list'.
>>> 
>>> 5.  Add translations 'pakfire resolvedeps wait', 'pakfire dependencies found' and 'pakfire no dependencies found' to use on install and remove confirmation pages.
>>> 
>>> 6.  Add new translations 'pakfire confirm updates' and 'pakfire updating' for new upgrade confirmation page.
>>> 
>>> 7.  Update pakfire.cgi to use 'pakfire upgrade', 'pakfire install', 'pakfire updates' and 'pakfire refresh list' instead of 'upgrade', 'install', 'available updates' and 'calamaris refresh list'.
>> The translation issues seem to be a much bigger problem than I thought.
>> 
>>> 8.  Update pakfire.cgi to convert icons to buttons on the main and confirmation pages.  Disable Install, Remove and Upgrade buttons if nothing to do.
>> Hmm, I think this could become a bit confusing, because even though there might not be anything to do right now, a greyed-out button will let the user know where to go whenever there is something to do.
>> 
>> I am also concerned about potential layout breakages if there are so many changes. The entire web UI is incredibly based on tables and removing a cell somewhere might either mess up the layout or you will need to add a lot of code for simple things. I would rather look at investing this time to replace the web UI as a whole.
>> 
>>> 9.  Update pakfire.cgi to add confirmation page for upgrades.  The confirmation page will do a 'pakfire update' to ensure that the local pakfire database is current and then display updates to be made and request confirmation.  The box title will be 'pakfire upgrade'.
> The buttons will still be there but greyed out, so no layout changes.  The Install and Remove buttons will be activated by the onchange <select> event so when the user selects an add-on the button activates and the user gets kind of a "Click here next!" indication.  The Upgrade button will be active if there is anything to update displayed in the 'Available Updates:' box.  In either case, the confirmation pages won't be displayed if there is nothing to do.

Okay.

>> Agreed.
>> 
>>> 10.  Update pakfire.cgi to change box titles for install and remove confirmation pages from 'request' to 'pakfire install' and 'remove'.
>>> 
>>> 11.  Update pakfire.cgi to change 'abort' on confirmation screens to 'cancel'.
>>> 
>>> 12.  Update pakfire.cgi install and remove confirmation pages. Display 'pakfire resolve wait' while 'pakfire resolvedeps' is running.  Only display 'Need to install...' lines from 'pakfire resolvedeps' output.  Remove spaces between resolvedeps output lines to tighten up the output.  Display "Dependancies found:' before list of dependancies or 'No dependancies found.' if none found.  The 'Checking
>>> 
>>> 13.  Update pakfire.cgi to change 'uninstall' to 'remove' on confirmation page.  The main page uses 'remove' for the minus sign, but the confirmation page uses 'uninstall'.
>> I never know which one would be the best term. SuSE is even using “erase”. I think remove makes the most sense and is also visually different from “install” - unlike “uninstall”.
>> 
>>> 14.  Update pakfire.cgi to adjust some spacing and alignment.
>>> 
>>> 15.  Add missing translations for the cases where the translations are English=>English instead of English=>Language.
>> Yeah, this is a difficult topic. In many languages there are native words for things, but everyone is using the English term as it is much easier and to the point. So in German you would still use “Updates” although there is a word like “Aktualisierungen”. So be careful with Google translate :)
>> 
>>> 16.  Clean up
>>>         Delete 'upgrade' tr.  It is now unused.
>>>         Delete 'available updates' tr.  It is now unused.
>>>         Delete 'abort' tr.  It is now unused.
>>>         Delete 'request' tr.  It is now unused.
>>>         Delete 'uninstall' tr.  It is now unused.
>>>         Delete 'pakfire possible dependancy' tr.  It is now unused.
>>>         Delete 'pakfire core update auto' tr.  It is not used.
>>>         Delete 'pakfire health check' tr.  It is not used.
>>>         Delete 'pakfire update daily' tr.  It is not used.
>> Agreed. You know about “./make.sh lang”?
> Nope, did not know that.
> 
> I'll run that before sending patches with tr changes so that issues/missings get updated.

Thank you.

>>> Note on translations:
>>> 
>>> I am doing translations with multiple web based translation utilities.  Where the results don't match between the utilities, I look for other similar translations in the applicable *language*.pl file and pick the one that seems to be most in context or consistent.
>> I think this is a good start. We have people on the team who can help with German, Dutch, maybe a bit of French. There are some Italian people on the forum which can help. For the rest, I would consider those translations abandoned and I think it is fine to just do nothing here and the software will automatically put the English version which at least is correct.
>> 
>>> Where titles and button text have multiple words.  I capitalize the words.  For example 'Available updates:' becomes 'Available Updates:' and 'Liste aktualisieren' becomes 'Liste Aktualisieren'.
>> Yes, I like the words being capitalised in English. It looks a bit wrong to me in German, because only nouns are capitalised. Not sure how people feel about other languages.
> I'll change the German back to "Liste aktualisieren".  Hopefully there will be enough language review from the team to keep me from doing anything incredibly weird.  :)

*fingers crossed*

>> 
>> Best,
>> -Michael
>> 
>>> ==========
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
> Regards,
> Stephen