[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Devboard 82 Release
Thanks for your reply.
Ok, I see that from your point of view this is a good idea but... :)
I have a whole load of config files for various stuff which eventually ends up
in the /etc directory during a 'make install' (in pre 192 releases) and I have
been putting these in the ~/axis/devboard_82/files directory and adding the file
paths in the correct section of makefile. All nice and easy.
What should I do for 192? I don't really know what a 'package' is; is it just
collection of files with its own makefile? Should I make a 'package' containing
my config files and allow the Makefile to do the work? Or should I copy the
'files' section of the old makefile (with only my own files there, of course)
to the new makefile? Actually, that does not sound like a good idea come to
think of it.
I think I need a little guidence here. I don't wont to do something that might
interfere with the overall system.
Thanks for your time
Anders Torbjorn Johansson wrote:
> Hello Bob,
> Unfortunately there is no detailed information about this in the releaseinfo.
> All local files (the ones that used to exist in the files-directory) are
> installed by packages, as example the webpages are installed by
> packages/web/devboard/.... The reason is that we in the future will
> distibute all packages separatly which mean that the only thing that
> is provided in the release is a configure-file (which defines all packages
> for the release and their versions) and a kernelconfig. All packages are
> fetched by the configure-script from our web/ftp-server and updates for
> specific applications will just be a matter of changing the revision
> in the configure-file.
> Best Regards,
>>Behalf Of Robert Hibberdine
>>Sent: den 10 juni 2004 16:35
>>Subject: Re: Devboard 82 Release
>>Just downloaded and looked at the new 192 release. The
>>'files' directory in no
>>longer there. Are there any docs on how this release has been