This is the mail archive of the
ecos-discuss@sources.redhat.com
mailing list for the eCos project.
Re: creating components
- To: rrv at tid dot es
- Subject: Re: [ECOS] creating components
- From: Bart Veer <bartv at redhat dot com>
- Date: Mon, 9 Oct 2000 14:44:32 +0100
- CC: ecos-discuss at sourceware dot cygnus dot com
- References: <39D2F47D.FBAD61B2@tid.es>
- Reply-to: bartv at redhat dot com
>>>>> "Rafael" == Rafael =?iso-8859-1?Q?Rodr=EDguez?= Velilla <Rafael> writes:
Rafael> I have read that the 3 initial letters of the name of
Rafael> every component reflects who is the programmer of that
Rafael> component. It says that even when a minor variation of a
Rafael> component has been made, the programmer should change
Rafael> the initial letters. Is this an strict rule?
Is this a reference to the Component Writer's Guide? Specifically
http://sources.redhat.com/ecos/docs-latest/cdl/language.naming.html
There is a convention for naming packages such that the first three
characters identify the developer of that package (typically a company
rather than an individual). This is just a convention, not a hard
rule. If a third party vendor chooses to ignore the convention then
there is an increased risk of a name clash, causing problems for users
of that package - but package developers may choose to take that risk.
However the package name should not change when you release a new
version. For example the kernel package was called CYGPKG_KERNEL in
release 1.0 of eCos, is still called CYGPKG_KERNEL today, and will be
called CYGPKG_KERNEL for the foreseeable future. What does change is
the value associated with that package, and that value is reflected in
the directory structure of the component repository. For more
information on this topic please see chapter 2 of the Component
Writer's Guide.
Bart Veer // eCos net maintainer