Is there a version check for proprietary plugins?

Asked by Johannes Meixner on 2008-04-24

Imagine a user has an older HPLIP version >= 2.7.10 installed
and connects now a ZJStream printer (e.g. Laserjet 1020)
and runs the hp-setup tool of his old instlled HPLIP version.

Is there a version check that the right version of the
proprietary plugin is downloaded which matches to his
actually installed HPLIP version?

For how long does HP provide the proprietary plugins
for older HPLIP versions at all and would the exact
download URL (i.e. what is used by hp-setup)
be unchaged during all the time (or is there at least
an automated redirect by the server at HP so that
the hp-setup download works)?

Background information:

Our next major version of our business products
(SLES and SLED) will provide HPLIP >= 2.7.10.
But usually there is no package version upgrade
during lifetime of a business product which is
about 5 years (and it could be even longer).

This means that e.g. in year 2013 it might happen
that a user installs SLED from scratch on his new
computer and now wants to set up again his
Laserjet 1020 which he owns since a long time.

O.k. - o.k. of course I know that a LaserJet 1020 crap
will most likely not survive such a long time so that
my example is only theoretically but I hope you got
the idea behind ;-)

Seriously:
It is really very important for us what happens
regarding long-time support for HPLIP.

Question information

Language:
English Edit question
Status:
Answered
For:
HPLIP Edit question
Assignee:
No assignee Edit question
Last query:
2008-04-25
Last reply:
2008-05-12

Hey Johannes,

We are going to be revamping the plugin system soon and your suggestions are highly respected and appreciated.

Although I can't guarantee how this will be implemented we will be looking at a process for plugin versioning in the future.

If you have any other suggestions/comments please feel free to let us know.

Aaron

Johannes Meixner (jsmeix) said : #2

I would appreciate it if it is implemented in the next few month.

Reason:
If we get a HPLIP version in our next major version of our business
products (SLES and SLED) without plugin versioning, we are most
likely bound to this HPLIP version (a version upgrade for our business
products is only possible for severe issues and I guess a few models
which are perhaps not directly meant for business usage do not matter
sufficiently to risk incompatibilities in case of a version upgrade).

I think as a first step it would be perfectly sufficient when hp-setup
does at least a plugin version test and shows a meaningful error
message if the plugin which is available for download does not match
to the actually installed HPLIP version.

Then as a second step a full featured plugin versioning system could
be implemented but then there is no time pressure when at least
a simple plugin version test is already implemented.

What do you think?
Is a simple plugin version test possible soon?

Launchpad Janitor (janitor) said : #3

This question was expired because it remained in the 'Open' state without activity for the last 15 days.

Johannes,

We're working on possibly implementing the plugin feature for the next release.

Thanks!

Aaron

Can you help with this problem?

Provide an answer of your own, or ask Johannes Meixner for more information if necessary.

To post a message you must log in.