On Tue, Jan 27, 2009 at 1:27 PM, Andreas Tille <til...@rki.de> wrote: > On Tue, 27 Jan 2009, Mathieu Malaterre wrote: > >> $ echo "med" | od -b >> 0000000 155 145 144 012 >> >> 1.3.6.1.4.1.9586.155.145.144 >> >> This would be the toplevel (root) of all UID generated from the >> dicom3tools package. > > Hmm, I'm not sure whether this helps. May be I missunderstood the > problem but is the UID per *package* or per *installation*. IMHO > assigning a UID to a Debian package makes not much sense because > it is finally interesting for the organisation which *installs* > this package. So rather than generating the UID in the build process > it should be created in the postinst and the admin who is installing > the package should register this UID at IANA. > > So we should find a way how to find some reasonable means to > *generate* a UID which was not registered yet. Asking for an > Organisation name per debconf and perhaps using a part of the > MD5 sum or something like that and *combining* it with a > *template* for the package comes to mind. > > Did I missed something?
the ideal solution would be indeed that a conf file would indicate what is the root UID being used. GDCM has one, DCMTK has one. David Clunie (author of dicom3tools) has one, SIEMENS, GE, Philips, my actual company. the problem is for one time user, converting a MINC file to DICOM. Any larger organisation would have there own UID, but would need to -painfully- recompile dicom3tools. -- Mathieu -- To UNSUBSCRIBE, email to debian-mentors-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
