https://bugs.documentfoundation.org/show_bug.cgi?id=172592

            Bug ID: 172592
           Summary: deb/rpm repositories structure
           Product: LibreOffice
           Version: unspecified
          Hardware: All
                OS: Linux (All)
            Status: UNCONFIRMED
          Severity: enhancement
          Priority: medium
         Component: LibreOffice
          Assignee: [email protected]
          Reporter: [email protected]

Description:
Nowadays it is, at every distro update, always more easier to install a piece
of packaged software from its own repository.
We provide a (well) structured repository, but it doesnt follow the deb/rpm
structure format.

Would be possible to structure (maybe a subdomain with simple softlink to the
main repository) a compatible deb/rpm repository structure? In that way user
may simply "install" the LO official repository, and they will get simple
updates as soon as available.

Government are going to adopt linux in their department; as office suite, we
should try to provide the best/easier experience to their IT (especially in
simple cases as this one) to adopt LO as software, assuring them an easy way to
integrate/automatize LO software updates in theirs infrastructure.
Perfectly aware that they run their own personal repository to get the max
awareness about which version is pushed to their PC, but if we provide
something like that, they should in anycase "download" the software, and in
some case, it would be possible to reach also the opportunity of a new mirror
kept alive from organization to help with LO infrastructure load.

Steps to Reproduce:
1. install manually without the opportunity to install from the distro's
package manager

Actual Results:
Download from site, point to the deb/rpm and install it (uninstalling the
previous version first).

Expected Results:
Just run distro's package manager update command and it does "its own magic"


Reproducible: Always


User Profile Reset: No

Additional Info:
N/A

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to