Hi Eric,
that's really good news!!!
I try to upload in the next 24h hours.
Many thanks
Andreas.
On Mon, Feb 20, 2012 at 07:23:21PM +0100, Eric Maeker wrote:
> Hi,
>
> I've just released a new upstream and updated the debian files in the
> Debian Med svn.
> Can anyone help us to upload t
Hi,
I've just released a new upstream and updated the debian files in the
Debian Med svn.
Can anyone help us to upload this new version.
There are no licensing issue with this new upstream.
Thanks
-
Eric Maeker, MD (FR)
http://www.ericmaeker.fr
http://www.freemedforms.com
--
To UNSUBSCRIBE
> that user can test functionnalities).
Great. This will keep FreeDiams in main!
> For the current and the previous versions, we can not provide a free package
> and a non-free.
While this would ba a bit sad I care more for the future than for the
past. We might deliver a FreeDiams t
guess not because it would probably need a
> change in debian/control, but just to make sure. I would plan to split
> the original upstream source into the database part for non-free and
> the code for contrib - but needs to negotiate this with upstream.
For the previous release of
Hi Alexander,
On Tue, Jan 24, 2012 at 06:34:42PM +0100, Alexander Reichle-Schmehl wrote:
> > I'm not an FTP master, though.
>
> As far as I can see, the package is indeed distributable, but not fit
> for main.
Thanks for inspecting the package. While this is not the best possible
option it is a
Hi!
* Philipp Kern [120120 15:41]:
> > In case the version in Squeeze would be considered free also all
> > other versions are free (which would be *really* good news). So
> > please, please prove me wrong in my opinion that this database is
> > not distributable. I'm specifically concerned ab
On Fri, Jan 20, 2012 at 03:26:08PM +0100, Andreas Tille wrote:
> Please seek for "drugs/master.db" to find the relevant licensing
> information about the compilation of data. As far as I understand
> upstream upstream the database in the old version is featuring the same
> data sources in older ve
eeze, too).
> > In CC.
>
> squeeze doesn't have a master.db. As for the other drugs/*.db I don't think
> they are actually copyrightable (at least in the US, being a database
> collection of public information).
The overworked debian/copyright file for the
Hi Sebastian,
On Fri, Jan 20, 2012 at 09:58:42AM +0100, Sebastian Hilbert wrote:
> > it turned out that the database which is used in freediams (file
> > global_resources/databases/drugs/master.db) is a compilation of data
> > with different licenses. Some of the original dat
Package: ftp.debian.org
Severity: normal
Hi,
it turned out that the database which is used in freediams (file
global_resources/databases/drugs/master.db) is a compilation of data
with different licenses. Some of the original data have non-free or
unclear licenses. After a discussion on the
readers and non-free plugs or mp3.
>> - do I really have to care about anything if a hacker (involved in a law
>> affair
>> of copyright) points me as provider of the data ?
>
> This question is too complicated for me.
>
> In any case it reminds me that we need to a
> > this please explain more verbosely why to make me understand.
> >
> > In addition to this GPLed code try to add a minimum set of free data to
> > enable some basic operation. Could be a package freediams-data-free (or
> > whatever you might like to call it).
>
> > On Wed, Jan 18, 2012 at 02:28:51PM +0100, Eric MAEKER wrote:
>> >> I can provide a 100% free database using the only FDA drug database, even
>> >> if in this case, FreeDiams/FreeMedForms lost its main useful (and
>> >> powerful) part. This does not make
On Wed, Jan 18, 2012 at 02:28:51PM +0100, Eric MAEKER wrote:
> I can provide a 100% free database using the only FDA drug database, even if
> in this case, FreeDiams/FreeMedForms lost its main useful (and powerful)
> part. This does not make sense.
>
> Should we place the FreeM
> The following database are not free enough for Debian:
...
> - atc classification
The ATC part in FreeDiams which has been obtained from
GNUmed is free enough because the data has been created by
- manually typing in data
- screen-scraping consumer/end-user facing websites
Karsten
ction database
- atc classification
- icd10 classification
- all other drugs database (than FDA)
I can provide a 100% free database using the only FDA drug database, even if in
this case, FreeDiams/FreeMedForms lost its main useful (and powerful) part.
This does not make sense.
Should we plac
On Thu, Nov 17, 2011 at 03:28:05PM +0100, Karsten Hilbert wrote:
> On Thu, Nov 17, 2011 at 02:49:42PM +0100, Andreas Tille wrote:
>
> > Not really. If I undrestand correctly FreeDiams need some database.
> > You build a database which is created from data which are distribute
On Thu, Nov 17, 2011 at 02:49:42PM +0100, Andreas Tille wrote:
> Not really. If I undrestand correctly FreeDiams need some database.
> You build a database which is created from data which are distributed
> under a DFSG free license and ship it with FreeDiams. Please make sure
>
t create two
> master.db, I don't have time for !!
Well, I can not decide about your time. :-)
> I still suggest that FreeDiams/FreeMedForms comes without any data and
> FreeDiams/FreeMedForms manages this lack of data. So that I've got less code
> to write for the Win/Mac/Lin
gt; Ok so the idea is to remove the master.db from the source package and create
> inside the app a data package manager that will download non-free data from
> my personnal server. No ?
Not really. If I undrestand correctly FreeDiams need some database.
You build a database which
On Thu, Nov 17, 2011 at 01:56:10PM +0100, Eric MAEKER wrote:
> > Well, we could try to create an installer package as it is done for
> > other non-free stuff.
>
> This is a good solution in postinst/postrm ? That will save me from coding a
> data-pack manager.
I'd suggest releasing a separate so
t you
regard as useful for your other users. For Debian its is enough to
specify the exact files to move inside a file called
debian/freediams-theme.install
(or whatever the name should be). Just move the according lines from
debian/freediams.install and create a new entry for the
On Thu, Nov 17, 2011 at 01:01:51PM +0100, Eric MAEKER wrote:
> >> says "unknown". This license should be clarified otherwise it is simply
> >> non-free and this non-free license of a part of the file master.db makes
> >> the whole file non-free.
> >
> > Well the site does not mention any license..
prefer to see the source data files shipped
> > inside the FreeDiams source tarball and create the database in the build
> > process.
>
> Impossible, the build process requires user interaction and checking.
Well, I have no idea about this but I would love if users would be
served wit
a private package from
> my server (if the database is missing).
Well, we could try to create an installer package as it is done for
other non-free stuff. What we also can do is (probably, I did not read
the license really carefully) to ship the package under Debian non-free.
The problem w
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) no
adnwidth to ship copies of
> > 64MB files in different packages
>
> Yop I've already thought about this.
>
> > 2. Making FreeMedForms Depend from freediams-data (arch=all) package
> > which basically has the file above has payload. Other files
> > i
Hi Eric,
On Wed, Nov 16, 2011 at 05:25:23PM +0100, Eric MAEKER wrote:
> Ok uploading FreeDiams 0.6.2.
> This upstream will fix all bugs we notified during the packaging of v0.6.0.
Great.
When I had a look into FreeMedForms I noticed that it contains the very
same file
global_res
; they are automatically installed by make install.
Hmmm, this automatic install moves to debian/tmp - I simply used
dh_install to copy files straight from original files which probably
serves the same purpose and makes manual copying superflous as well.
> I'll try to commit the so
base url corrected too.
I think that in rules: override_dh_install: you do not need to copy doc files
they are automatically installed by make install.
I'll try to commit the source package today. FreeDiams version will be upgraded
to v0.6.2.
>> All the FreeMedForms team would like to t
plan might consider some minor
release soonish. Otherwise we might go with the current version and
trust that it will be fixed later.
> All the FreeMedForms team would like to thanks you for the time you've spend
> and you still spend on the Debian packaging of the FreeDiams and FreeM
Le 8 nov. 2011 à 20:57, Andreas Tille a écrit :
> Hi Eric,
Hi Andreas,
Thanks for your clarifications and corrections.
> as you can see I have commited a bunch of changes. I admit I'm a bit
> astonished that ftpmaster was originally accepting FreeDiams - there was
> a l
Hi Eric,
as you can see I have commited a bunch of changes. I admit I'm a bit
astonished that ftpmaster was originally accepting FreeDiams - there was
a lot of information missing in debian/copyright.
I think the package is close to ready now. There is one thing I would
like to fix y
Hi Eric,
thanks for keeping us updated about your activities. I'll start
traveling in a couple of minutes (=beeing offline today) and will see
what I can do for FreeDiams and FreeMedForms (in this sequence of
priorities) and keep you updated how far I went.
Kind regards and congratulatio
Hi all,
We have updated the FreeMedForms project:
FreeMedForms EMR reaches the stable stage (0.6.0)
FreeDiams reaches a new stable version (0.6.0)
The debian files were updated on the Debian Med SVN. And we are looking for
sponsor to upload the packages.
Thanks
-
Eric
Hi all,
FreeDiams is updated to a stable version: 0.6.0. Since last v0.5.4, lots of
news mainly in the drug engines and the drug database architecture.
Website updated.
http://www.freemedforms.com
Packages uploaded (Mac, Win, Sources), and PPA building (oneiric already
compiled
On Fri, Apr 29, 2011 at 10:20:02PM +0200, Eric MAEKER wrote:
>
> I don't really know what is the best way to provide our alphas in the Debian
> Med world ?
It depends. There might be maintainers who upload alpha state software
to experimental. In the case of FreeDiams I do not
Hi all,
I'm working on an alpha release of
- FreeDiams (already included in Debian Med)
- FreeMedForms (not already available in Debian Med)
I don't really know what is the best way to provide our alphas in the Debian
Med world ?
Should we self-create package and give them to d
On Tue, Mar 15, 2011 at 08:21:24PM +0100, Sebastian Hilbert wrote:
> But for now I am fine with leaving this as is.
So I'll leave it as is. :-)
Thanks for your comment anyway
Andreas.
--
http://fam-tille.de
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subje
xtra metapackage.
There is hard reason and I am fine with leaving it as is. The reasoning was
that the project freadiams is logically split into data and client anyway by
providing a data package. So the suggestion was to rename the freediams
package to freediams-client.
From what I hear some
Hilbert wrote:
> Hi all,
>
> Please consider the following change.
>
> I would like to see a metapackage freediams which would install freediams-
> client and freediams-data.
>
> The current freediams package would be renamed to freediams-client and the
> newly cre
Hi all,
Please consider the following change.
I would like to see a metapackage freediams which would install freediams-
client and freediams-data.
The current freediams package would be renamed to freediams-client and the
newly created freediams package is a metapackage.
Why ? Well freediams
On Wed, Oct 06, 2010 at 08:30:28PM +0200, Eric MAEKER wrote:
> with debuild I have the following warnings
>
> W: freediams source: changelog-should-mention-nmu
> N:
> N:When you NMU a package, that fact should be mentioned on the first line
> N:in the changelog entry.
On Wed, Oct 06, 2010 at 11:15:11AM +0200, Karsten Hilbert wrote:
>
> Even the *.dsc ? I thought that was part of the build
> process. One never stops wondering.
Try the following:
apt-get source
rm *.dsc *.debian.tar.gz *.diff.gz
cd
debuild
after this you have a new *.dsc.
> >
On Wed, Oct 06, 2010 at 11:08:20AM +0200, Andreas Tille wrote:
> Nooo, not the *.dsc, *.build and *.changes file!!!
> They are auto generated and do NOT belong to the SVN.
Even the *.dsc ? I thought that was part of the build
process. One never stops wondering.
> > - fix Andreas' complaints ;-)
On Wed, Oct 06, 2010 at 10:18:59AM +0200, Eric Maeker wrote:
> > are happy with the status. I will have a look at it then. Currently
> > your download site is lacking the tarball - so
> >
> > uscan --verbose --force-download
>
> Of course I did not upload it ;)
But this would be helpful. ;-)
> Ah so I need to svn add and commit the dsc build and changes files to
> > freediams/trunk/debian/ ?
>
> Yep.
Nooo, not the *.dsc, *.build and *.changes file!!!
They are auto generated and do NOT belong to the SVN.
> > with my so little debian dev experience ;)
>
&
and commit the dsc build and changes files to
> freediams/trunk/debian/ ?
Yep.
> Wooo all of this is awfully complex
The result of that complexity is, however, the reliability
of the Debian platform.
> with my so little debian dev experience ;)
What I am doing is this:
- during develop
2010/10/6 Karsten Hilbert :
> On Wed, Oct 06, 2010 at 01:07:25AM +0200, Eric MAEKER wrote:
>
>> For FreeDiams 0.5.0beta-1, I can provide a source package (one file tar
>> gzipped) containing :
>> - freediams_sources_0.5.0beta.tgz (the cleaned sources)
>> - freedi
> Just commit your changes to the Debian Med repository and tell me if you
> are happy with the status. I will have a look at it then. Currently
> your download site is lacking the tarball - so
>
> uscan --verbose --force-download
Of course I did not upload it ;)
> fails to download the lates
On Wed, Oct 06, 2010 at 01:07:25AM +0200, Eric MAEKER wrote:
> For FreeDiams 0.5.0beta-1, I can provide a source package (one file tar
> gzipped) containing :
> - freediams_sources_0.5.0beta.tgz (the cleaned sources)
> - freediams*.dsc
> - freediams*.build
> - freediams*.c
On Wed, Oct 06, 2010 at 01:07:25AM +0200, Eric MAEKER wrote:
> Hi Andreas,
>
> For FreeDiams 0.5.0beta-1, I can provide a source package (one file tar
> gzipped) containing :
> - freediams_sources_0.5.0beta.tgz (the cleaned sources)
> - freediams*.dsc
> - freediams*.build
&
> Hi Andreas,
>
> For FreeDiams 0.5.0beta-1, I can provide a source package (one file tar
> gzipped) containing :
> - freediams_sources_0.5.0beta.tgz (the cleaned sources)
> - freediams*.dsc
> - freediams*.build
> - freediams*.changes
>
> Theses files were created
Hi Andreas,
For FreeDiams 0.5.0beta-1, I can provide a source package (one file tar
gzipped) containing :
- freediams_sources_0.5.0beta.tgz (the cleaned sources)
- freediams*.dsc
- freediams*.build
- freediams*.changes
Theses files were created with the Debian files from the Debian-Med svn and
>> I saw that the package depended FreeDiams GNU hurd? Is this a mistake / a
>> needed one?
>
> Where exactly did you found this? There might be a GNU hurd port for
> freediams but I have not found a sign that this is currently the case.
here:
http://packa
e two (official!) tarballs with one containing the
freediams code and one freediams-doc tarball.
Whatever you decide we should base the Debian packages on the official
tarball you are releasing and not on a mix from an officially released
tarball plus some "random" Wiki content.
> * Th
Hi all,
As usual, I am pleased to participate in Debian-Med.
I'm preparing FreeDiams 0.5.0 beta for Debian.
Le 1 oct. 2010 à 08:07, Andreas Tille a écrit :
>> I was wondering if it would be possible to recreate the packages from
>> Debian-Med's scripts and if the resul
his task as useful?
>
> How do you exactly define this task ?
Good question. I needed a task where I was able to cleanly put
drugref.org because we attempted packaging and I wanted to support the
project. Both seems to be moot now - but somehow I was thinking that
FreeDiams fits in the data
On Tue, Jul 13, 2010 at 09:19:08AM +0200, Andreas (Debian) wrote:
> as you can see, FreeDiams is now listed as "In new queue":
Great.
>http://debian-med.alioth.debian.org/tasks/data
>
> The fact that it serves perfectly as plugin into GNUmed and other
> practice m
Hi,
as you can see, FreeDiams is now listed as "In new queue":
http://debian-med.alioth.debian.org/tasks/data
The fact that it serves perfectly as plugin into GNUmed and other
practice management software let me think that it should also be listed
in the med-practice task (t
8. then a simple translation of the interacting classes will be needed
> (iam.db from code 000 to code 999) --> using a wiki page would be
> great and simple.
I probably do not fully understand yet how the interaction
code works inside FreeDiams.
I would have thought once English and F
On Thu, Apr 29, 2010 at 05:03:31PM +0200, Eric MAEKER wrote:
> For your information, the FDA database is fully integrated in
> FreeDiams 0.4.0. That allows everyone to prescribe with the US
> pharmacopea.
Congratulation on that !
I would think a worthy goal post 0.4.0 release wo
Hi all,
Don't worry FreeDiams v0.4.0 is about to be released. I still have
some changes to done on some parts of the code to release it. I still
need some days for that. A beta release is available and I need a
maximum of testings.
http://code.google.com/p/freemedforms/down
nks is a bug.
> > Question: If you say it is an "upstream" problem, do you want me to say
> > that FreeDiams includes copies of code from MedinTux?
>
> FreeMedForms project (including all derivatives like Freediams, FreeGIR and
> FreeAccount) is a full "
kes software better and
> finally it saves your own time once it is fixed.
Can you detail the bug please ? Are you talking about the symlink ?
> Question: If you say it is an "upstream" problem, do you want me to say
> that FreeDiams includes copies of code from MedinTux?
Free
dspecs/install.pri replace line 85 with
> applibs.files = $${BUILD_LIB_PATH}/*.1.$${LIB_EXTENSION}
>
> App will work fine without the symlinks. We don't need these links 'till
> these libs are private to FreeDiams.
I will try to have a look. Creating a patch using quilt is
ese libs are private to FreeDiams.
Kind regards
Andreas.
Eric
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Archive: http://lists.debian.org/1cd0bfdb-99ad-4001-bbf7-6ad40504f...@gmail.com
On Mon, Mar 29, 2010 at 04:29:15PM +0200, Eric MAEKER wrote:
> May be the install.pri adaptation is a better solution.
It would be the better solution ... if it would work. The approach I
tried first does not work, but the hack does. I'd prefer a clean
solution as well but I do not know the qmak
Le 29 mars 10 à 15:03, Andreas Tille a écrit :
Hi,
I worked around the RPATH issue of FreeDiams by patching[1] which is
not
a really clean solution but works. The patch file contains a
comment about
my previous more clean trial. Eric, perhaps you might like to read
more
about this
Hi,
I worked around the RPATH issue of FreeDiams by patching[1] which is not
a really clean solution but works. The patch file contains a comment about
my previous more clean trial. Eric, perhaps you might like to read more
about this issue[2].
There is one problem remaining in the final
On Mon, Mar 29, 2010 at 09:15:07AM +0200, Eric MAEKER wrote:
> Try in rules
>
> override_dh_install:
> make install
Sounds very reasonable. Sorry for introducing this problem by choosing
short dh command. While I made several positive experiences with this
change it opens a pitfall here.
On Sat, Mar 27, 2010 at 11:31:39PM +0100, Eric MAEKER wrote:
> 3) correcting debian/rules (read freediams build process documentation) :
Well, as I said, I have read the doc and I took over your old rules
files with this commend in the first place.
> From
> override_dh_auto_
Hi,
I found reason for the problem of building freediams with the current
SVN packaging stuff: Files will be installed into:
$(CURDIR)/debian/tmp/$(CURDIR)/debian/tmp/usr
I currently have no time to verify the reason for this, but anybody
with qmake experience and is interested in speeding
On Wed, Mar 17, 2010 at 12:23:03PM +0100, Karsten Hilbert wrote:
> I just wanted to know the state of affairs.
Perfectly valid request - I hope other people will do so in similar
cases as well.
> Sometimes such things are forgotten.
Not the cese here, but in general this is actually a real dange
On Wed, Mar 17, 2010 at 11:38:27AM +0100, Andreas Tille wrote:
> > I wonder what needs to be done to get FreeDiams into Debian
> > proper ?
> >
> > They've got .debs available which install cleanly on
> > Squeeze. Thus it is likely that there is an easily
On Wed, Mar 17, 2010 at 10:16:35AM +0100, Karsten Hilbert wrote:
> I wonder what needs to be done to get FreeDiams into Debian
> proper ?
>
> They've got .debs available which install cleanly on
> Squeeze. Thus it is likely that there is an easily
> debianizable tarball av
Hello all,
I wonder what needs to be done to get FreeDiams into Debian
proper ?
They've got .debs available which install cleanly on
Squeeze. Thus it is likely that there is an easily
debianizable tarball available somewhere.
Thanks,
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167
On Mon, Feb 15, 2010 at 02:30:22PM +0100, Eric MAEKER wrote:
> Hi Andreas,
>
> Thanks for your help.
SUre. As I told you when I had a look at verison 0.1.4. I have
seen that you regarded some of my hints but somehow I lost track
of freediams. Time to restart this effort now. ;-)
An
Hi Andreas,
Thanks for your help.
Eric
I'm in contact with Eric and will continue working on this task this
week.
Kind regards
Andreas.
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Arc
On Mon, Feb 15, 2010 at 11:56:24AM +0100, Karsten Hilbert wrote:
> If someone could work with upstream and eventually sponsor this
>
> http://freemedforms.googlecode.com/files/freediams_0.3.0_i386.deb
>
> package that would be great for GNUmed as we would like to
> use it as a dependency.
If someone could work with upstream and eventually sponsor this
http://freemedforms.googlecode.com/files/freediams_0.3.0_i386.deb
package that would be great for GNUmed as we would like to
use it as a dependency.
Karsten
--
GPG key ID E4071346 @ wwwkeys.pgp.net
E167 67FD A291 2BEA 73BD
Hi all,
Hi Andreas,
After some weeks of work, I'm proud to announce the release of
FreeDiams 0.3.0.
Sources, win package, deb package, mac package are available.
Please visit : http://www.freemedforms.com/
FreeDiams is a free, open source, BSD revised licenced, pharmaceutical
Hi Andreas,
Excuse me i'll be late for the repackaging of FreeDiams. Flu is
here !!! Full of work...
I'll keep you inform soon.
Eric
--
To UNSUBSCRIBE, email to debian-med-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
Hi Eric,
I had another look into FreeDiams and I would like to propose some
changes for your upstream tarball which will turn out to be very helpful
for every Linux user and specifically for clean Debian packaging.
1. Please make only those files executable which really are
intended to be
On Fri, Oct 23, 2009 at 08:56:05PM +0200, Eric MAEKER wrote:
>> As I realised you are using the file debian/changelog to describe what
>> you have changed in FreeDiams. But this is not the intention of the
>> __debian__/changelog file. This file just describes the changes
Le 23 oct. 09 à 19:28, Andreas Tille a écrit :
On Tue, Oct 20, 2009 at 09:16:55PM +0200, Eric MAEKER wrote:
I've released sources of FreeDiams v0.1.2 (which is mainly a debug
release).
I have seen you even released v0.1.4 - at least guessing from your
commit to the packaging SVN.
I&#x
On Tue, Oct 20, 2009 at 09:16:55PM +0200, Eric MAEKER wrote:
> I've released sources of FreeDiams v0.1.2 (which is mainly a debug
> release).
I have seen you even released v0.1.4 - at least guessing from your
commit to the packaging SVN. I would like to clarify something and I
hop
Hi Eric,
there is no need to CC me in your mails, I'm reading the list carefully. ;-)
On Tue, Oct 20, 2009 at 09:16:55PM +0200, Eric MAEKER wrote:
> I've released sources of FreeDiams v0.1.2 (which is mainly a debug
> release).
Fine. Build is just running on my box. I'
Hi all, Hi Andreas,
I've released sources of FreeDiams v0.1.2 (which is mainly a debug
release).
I've compiled it with my old rules/control because I've had a lot of
errors when trying to use the new ones.
Can you try a compilation with the "three package" meth
et the three binary packages if you unpack your source tarball
>> checkout the debian directory of freediams from SVN copy it to
>> the unpackage tarball and say `debuild` there. That's basically
>> all.
> Yes but I'd like :
> - only one package for the download page
m afraid I do not understand the question. What exactly is
repro?
You get the three binary packages if you unpack your source tarball
checkout the debian directory of freediams from SVN copy it to
the unpackage tarball and say `debuild` there. That's basically
all.
> Oh I understand,
date the
version, or at the first start up.
This is not really annoying.
I must add a start message like this : "FreeDiams MUST NOT BE USED
for
automedication, please contact your doctor."
I have no idea whether this is needed or not. You might discuss this
issue on the Debian
On Fri, Oct 16, 2009 at 10:36:04AM +0200, Eric MAEKER wrote:
> So, I've made some bug corrections, files properties corrections and
> some improvements in FreeDiams. These are not yet published.
I'd suggest we try the same packaging stuff on your new version.
Or is there anythin
inform of legal issues in Open Source software.
> I must add a start message like this : "FreeDiams MUST NOT BE USED
> for automedication, please contact your doctor."
Ah, I see. This is less an issue with users as such rather
than with non-doctor users. I agree you better include such
a
Hi Andreas, Hi all,
So, I've made some bug corrections, files properties corrections and
some improvements in FreeDiams. These are not yet published.
Le 4 oct. 09 à 22:33, Andreas Tille a écrit :
I commited packaging stuff for FreeDiams which splits the single
binary
into two and
Hi,
I commited packaging stuff for FreeDiams which splits the single binary
into two and also adds a doc packages. I'm not completely happy with
this because when activating the rpath patch the dynamic libraries are
not found in the end. This might be investigated later.
I have a que
.
> But this is an issue.
No problem. For this purpose we like to provide help in the Debian Med
team.
> Can I add your contribution into the About page of FreeDiams/
> FreeMedForms (including public mail) ?
I don't really mind - mentioning the Debian Med team might make
sense.
>
I have one question: You installed
global_resources/databases/drugs/drugs.db
This the general database --> /usr/share/freediams
but
global_resources/databases/drugs/dosages.db
This is a personnal database created by the application on the first
start up --> $home/.freediams/dat
.
> But this is an issue.
No problem. For this purpose we like to provide help in the Debian Med
team.
> Can I add your contribution into the About page of FreeDiams/
> FreeMedForms (including public mail) ?
I don't really mind - mentioning the Debian Med team might make
sense.
>
ut the reasons to do so in the
net which I do not want to repeat here. I'd happily volunteer to do
this change because I'm afraid that you are not as experienced than me
in this kind of stuff.
Eh eh ! You already know me well ;)
Yes thank you for all your help.
Can I add your contr
1 - 100 of 110 matches
Mail list logo
