Comment 45 for bug 193818

if i understand correctly, gnome-scan intends the following design:

the functional backend:
- libgnomescan

providing functionality for various frontends:
- flegita, a standalone program for scanning documents
- flegita-gimp, a gimp-plugin for tight integration with the gimp
- other frontend programs yet to come, including those from 3rd party developers

---

principally this might be a good packaging structure on the long run. but right now, libgnomescan is not ready for it's intended use as a basis for scanning applications because the api/abi is not considered stable. it is thus not reasonable to package it as a library. i suggest to include it with flegita.

the options for flegita-gimp are to either include it with flegita or to make it a separate package. i prefer the first approach because it means just one package. for one thing i recently learned that it is beneficial to spare unnecessary packages and moreover the whole "gnomescan thing" is just one product right now.

---

i suggest a single package. i'd call it gnomescan, because it is a catchy name and established with the community. gnome-scan is acceptable, too. however it causes some overhead with transitional packages and has not been used "in the wild" yet. i could live with flegita, but it is not catchy or descriptive. furthermore it is the name of one part of the project only.

---

@Philipp: from a packaging point of view, is it ok to have one "gnomescan" package bundling all the "gnomescan stuff"? is it an advisable approach to do it as described above and split the package when libgnomescan becomes stable and useful on it own? would you do the packaging?

@Étienne: is this one-package-approach ok for you? can we call it gnomescan? are we supposed to call it gnome-scan? or should it be named flegita?

please comment timely, so work can start soon :)