[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: Tcl packaging guidelines

On Tue, 2007-02-06 at 10:42 -0800, Michael Thomas wrote:
> Following the precedent set by perl, python, and ruby, I've drafted a 
> set of proposed guidelines for Tcl packages.

> http://fedoraproject.org/wiki/MichaelThomas/Tcl
> The main motivation behind these guidelines is 
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=226893
The changes to enable this look sensible to me.

> These proposed guidelines will require changes to most of the
> existing 
> Tcl extensions in Fedora, as the installation directory for 
> arch-specific packages will need to be changed from %{_libdir} to 
> %{_libdir/tcl8.x.  Since Tcl was recently upgraded from 8.4 to 8.5a5
> in 
> rawhide, this seemed like a suitable time to make such changes.
> I'd like to get any feedback on this proposal before I submit it to
> the 
> Fedora packaging committee, hopefully in time so that the changes can
> be 
> made before the F7 release.

I'm not a tcl/tk user so this comment is based on other guidelines
rather than the specifics of tcl/tk:

== Naming Conventions ==

It is common for Tcl applications and extensions to begin with a 'tcl'
or 'tk' prefix in the upstream name.  Fedora Tcl packages should follow
this convention.  If the upstream name does not contain the 'tcl' or
'tk' prefix, then it is only necessary to add one if the upstream name
is inappropriately generic.  For example, the 'thread' extension to Tcl
is named 'thread' upstream, but is named 'tclthread' in Fedora.  The
upstream name for the 'bwidget' extension is uncommon enough that it
does not need to contain the 'tcl' or 'tk' prefix in the Fedora package

* Other languages use $LANGUAGE-$MODULE naming.
* All modules in perl, ruby, and php are using the $LANGUAGE- prefix,
there has been talk of removing the python exception (ie: having
python-pygpgme instead of pygpgme) as having all modules use
$LANGUAGE-$MODULE makes it easier for endusers to find modules written
for the language they are writing their program in.

So I'd propose:
* For modules, tcl-thread and tcl-bwidget.  Possibly tcl-tk but someone
with more experience with tcl/tk will have to tell me if that makes

Applications do not need to have the language prefix as users of the
application do not need to know what language it is written in.


Attachment: signature.asc
Description: This is a digitally signed message part

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]