Hi Rob,
Thanks for tour feedback on the packages.
> About the name of the packages: is the '-dev' in the name just for
> testing and will is disappear in the real release?
No, all the "dev_20081015" part is taken from the VERSION Makefile's param.
So we can put what we want. For the beta, I was thinking about "0.1beta"
(and maybe if needed, "0.1beta2", ...). For the final release, "0.1". Do we
agree ?
(and why '-' not '_' ?)
This is mostly what I see. "-" seperate description part of the package
("jallib", "devices", the version), "_" is used to have spaces for the
description part. For example, if "jallib" project was named "jallib is the
best", we would have had "jallib_is_the_best-0.1.tar.gz" and
"jallib_is_the_best-devices-0.1.tar.gz".
I had not intention to do this, but it is also impossible on my eCS
> system because of the Linux specific commands in the makefile.
Yeah, sorry for that. Maybe one day we'll create a cross-platform distrib
script. For now, I consider having the recipe (automatic) is enough.
> Q: I thought the command lines in a makefile must start with a tab
> character for GNU make. Not (anymore)?
Still have to have tabs. This is the case for our Makefile (unless I missed
something). Except (almost except) for the "for" loop within the Makefile.
Lines end with a "\", so for make, it's still the same line. It's a way to
indent things within a Makefile. (you've probably noticed I use Makefile
just as a way to build a shell script, with targets...).
> > Here I made TODO list. Feel free to correct it, add more, etc... This
> would
> > be very helpful to know which issue/point/decision/etc... still need to
> be
> > dealt with. Since we decide to release, lots of "sleeping" points have
> come
> > at the surface, which is good. Now, we have to deal with them so we can
> Get
> > Things Done, and Release ! :)
>
> I think I have to give priority to the device files to get the blink
> files working. I expect to need quite some time for a solution for the
> pragma fuse_def for the 18Fs. That is when I try to fix the dev2jal
> script. An intermediate solution could be to validate/release only some
> specific 18F device files. Eur has proposed some (3 IIRC), but is that
> be 'good enough' for the first beta? Personally I would like to release
> more, but that requires more time!
My take is to let the things as they are now and release. My worry is if the
device files change, ideally we would need to run all tests again, just to
be sure this is still working. The device files' stability is the first step
before testing and releasing. Maybe between the beta and the final, you can
adjust these. But it's up to you, just tell us what you decide !
This only affect the "jallib-devices" package, so another option would be to
add information about defective device files in the README, as known bugs,
and even links to the issue tracker. That way you release all, some are
defective but users are informed, and may be able to help/test your
updates/corrections.
> TODO, for the beta:
> > * README file for device files and blink files. It will selectively be
> > included into the jalliv-devices package.
>
> Should the readme for the device files contain different info or be an
> ASCII-text subset of 'devicefiles.html'?
About this, I can create a "doc" directory, and put only the
devicefiles.html. The README is more about describing the package structure:
* what found on "lib"
* what found on "blink"
* not all are tested, if users have tested some of them, they should
report, etc...
* there's a testing matrix to know how supported are the PICs (link)
* etc...
Again, this is a proposal, just add whatever you feel important to put in
this.
Cheers,
Seb
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the Google Groups
"jallib" group.
To post to this group, send email to [email protected]
To unsubscribe from this group, send email to [EMAIL PROTECTED]
For more options, visit this group at
http://groups.google.com/group/jallib?hl=en
-~----------~----~----~----~------~----~------~--~---
