On Fri, Jul 16, 2004 at 02:59:35PM -0500, [EMAIL PROTECTED] wrote: > hi all, > > I did some research on tclx and it looks like there hasn't been an explicit > release in 2 years, but one of the developers emailed me back and said to get > it from cvs. So I did and I can get it to work, so I have some questions on > packaging this beast... > > 1. How should I manage the source? Should I make a tar ball from a cvs > snapshot and call it their version number plus a date?
That sounds like a very good solution. > Something like this: tclx-8.4.0-snapshot-16072004.tar.gz Put the date in YYYYMMDD order, so versions will sort properly. Also could cut down the verbosity a bunch: 8.4.0.cvs20030716 > 2. This beasty needs access to internal files from the tcl and tk > sources to build. I was thinking that the info file could grab tcl > and tk of the right version and build against those (using SourceN). > Then I would have a Depend that was NOT >= 8.4.6-2 but =8.4.6-2. > However this seems like a major pain to keep in sync. Does the resulting package (TclX) actually interact with the system's tcl/tk stuff? Or does it just leach some of its sources but not need tcl/tk at runtime? If the former, then you don't need those dependencies at all. If the latter, then...um... > Suggestions?!?!? I could loosen up the requirements to be =8.4.? > It should work against any 8.4 version, right? I don't know how well apt and dpkg and fink's dependency engines handle revisionless values (or even if they all do it the same way). Try it and report back? dan -- Daniel Macks [EMAIL PROTECTED] http://www.netspace.org/~dmacks ------------------------------------------------------- This SF.Net email is sponsored by BEA Weblogic Workshop FREE Java Enterprise J2EE developer tools! Get your free copy of BEA WebLogic Workshop 8.1 today. http://ads.osdn.com/?ad_id=4721&alloc_id=10040&op=click _______________________________________________ Fink-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/fink-devel
