On Thu, Nov 17, 2011 at 11:11:51AM +0100, Eric MAEKER wrote:
> 
> > IMHO this is quite equivalent to my proposed second solution - but it is
> > freediams-drugs (we do not have a freemedforms package yet).  If you
> > move master.db from freediams-data there is (byte wise) not much left
> > which rectifies an additional arch=all package.  However if you want the
> > name to be renamed to freemedforms-drugs that's perfectly OK for me.
> 
> Well whatever is the most simple... freediams-drugs or freemedforms-drugs

SVN is now featuring freediams-drugs with only one single file master.db.

> > This could be done but are there any pixmaps shared between FreeDiams
> > and FreeMedforms?
> 
> Yes
> 
> >  If yes, which ones are these common files?
> 
> I can include all the theme files used by all FreeMedForms project 
> applications in the FreeDiams source tarball and in all other sources tarball.

Whatever makes the most sense to you.  A separate tarball with those
themes / graphics is fine as well.  We just need to know which files
are common to more than one project.
 
> >> The third solution can make the updating process of data much easier for 
> >> me (if I can build only one package instead of all). But the third 
> >> solution needs me to update some part of my code and needs to be sync with 
> >> OpenSuse, Fedora, Slackware and... Or may be a `ln -s` can be the solution 
> >> to access to theme/databases. We should try this.
> >>    eg: ln -s /usr/share/freediams/database/drugs/master.db 
> >> /usr/share/freemedforms/database/drugs/master.db
> > 
> > This can be done for sure (in case we make freemedforms:
> >  Depends: freediams-drugs
> > )
> 
> Ouh yes we need to add this +++

Just commited something like this to freemedforms SVN.  I havn't checked
if this finally works, but if not we will at least not forget ...

Kind regards

        Andreas.

-- 
http://fam-tille.de


-- 
To UNSUBSCRIBE, email to [email protected]
with a subject of "unsubscribe". Trouble? Contact [email protected]
Archive: http://lists.debian.org/[email protected]

Reply via email to