Hi Ihar,
a valid point.
We'll consider this when we make a next release.
Ihar Hrachyshka wrote:
Hello guys!
I have a problem when trying to automate DirectFB fetching from
official DirectFB resources. I build directfb library with help of
OpenEmbedded build system.
When new DirectFB library version (1.2.N) arrives, it's placed into
Core/ directory on http server. All good, we can automate version
substitution etc. Our build script fetches sources and builds them
fine.
The problem occures when the next version (1.2.N+1) arrives: it's
placed into Core/ directory, and old one (1.2.N) is ***moved*** to
Old/ directory. Of course our build script is broken, and we need to
manually specify new - Old - place for URI we should fetch the source
from.
I'd like to ask if there a way to fetch specific DirectFB version that
will guarantee that its URI won't change when the new library version
arrives. If currently there is no such way then I'd like to propose
DirectFB developers (admins?) to rework their source deploying process
to be more distributor friendly.
Thanks in advance,
Ihar Hrachyshka [aka booxter].
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
--
.------------------------------------------.
| DirectFB - Hardware accelerated graphics |
| http://www.directfb.org/ |
"------------------------------------------"
_______________________________________________
directfb-users mailing list
[email protected]
http://mail.directfb.org/cgi-bin/mailman/listinfo/directfb-users
