May 2004 - crux-devel - lists.crux.nu

[clc-devel] [port update] Update (test) submission for XYZ
by clc-devel＠berlios.de 04 May '04

04 May '04

Your port submission has been marked 'fixed' General advise: Please don't answer to this message unless you are subscribed to the clc-devel mailinglist; reopen your original submission (set state to 'new') and add a remark instead Description: There is a new port for XYZ available at http://jw.tks6.net/files/crux/ports#XYZ (this is a test submission; notification goes to clc-devel for now)) User: anonymous http://crux.fh-regensburg.de/cgi-bin/cvstrac/tktview?tn=50 Remark: _2004-Apr-14 21:43:23 by winkj:_ {linebreak} add remarks to check notification ---- _2004-Apr-14 22:37:08 by winkj:_ {linebreak} Okay, this is a test of the notification. Port update submissions are sent to clc-devel for now. If theres a need for it, we might introduce a dedicated mailing list later, but as far as I can see this approach is better since everyone already subscribes to clc-devel (Johannes)

1 0

[clc-devel] Fwd: Re: libtiff [per@fukt.bth.se]
by Giulivo Navigante 04 May '04

04 May '04

On 05/04/04 12:54:42, Per Liden wrote: > On Tue, 4 May 2004, Giulivo Navigante wrote: > > note that hylafax (now in contrib) needs of binaries stuff from libtiff > > that your port delete by default :( > > > > why you wants to remove these binaries? > > It has always been the CRUX-tradition to remove files that aren't used, > aren't needed or otherwise just take up space. What is considered > unneeded is of course a matter of taste, but /usr/bin/* from libtiff have > been on my list of unneeded files. > > If you need these utils, why not create a libtiff-utils port? Since Per consider unneeded /usr/bin/* from libtiff, a libtiff-utils port seems to be useful. Does anyone want to start maintaining it? Regards. -- Giulivo Navigante GnuPG KeyID: E468396A

1 0

[clc-devel] [port update] alsa-xmms project obsolete -- port can be removed with no ill effects
by clc-devel＠berlios.de 04 May '04

04 May '04

Description: Alsa support was added to main xmms branch, since xmms-1.2.8. http://www.xmms.org/next_version.php Contact: nsteeves(a)softhome.net User: anonymous http://crux.fh-regensburg.de/cgi-bin/cvstrac/tktview?tn=63

1 0

[clc-devel] [port update] ocaml: 3.07pl2
by clc-devel＠berlios.de 03 May '04

03 May '04

Description: Hi, I believe latest version of ocaml is 3.07 patchlevel2. ( 3.07pl2 ). my httpup port here: http://www.varlock.com/tmp#ocaml Contact: sip(a)users.berlios.de User: sip http://crux.fh-regensburg.de/cgi-bin/cvstrac/tktview?tn=60

1 0

[clc-devel] Migration plan for CRUX 2.0
by Simone Rota 03 May '04

03 May '04

Hi everybody, many of you will surely know that Per has released a test version for CRUX 2.0 available at: http://www.fukt.bth.se/~per/crux/files/test/ ( for Per: works fine here with a fresh install, I was to scered by the release notes to try an upgrade ). Given that there's been some important change ( http://crux.fh-regensburg.de/cgi-bin/cvstrac/wiki?p=TwoZeroChanges ) and that many ports would need some adjustement, I was wondering if we have a simple plan for migration and testing before tagging the files for CRUX 2.0. I extended the "build all" script I used to test during the 1.2 >> 1.3 upgrade (now with real-time online progress and info). I plan a run as soon as the needed adjustements are done in all ports; the question is, should be begin tagging CONTRIB_2.0 just now or is it better to use a temporary tag for our tests? Other ideas? I think an upgrade path is important also for future releases, anyway, one spoon at a time, let's concentrate on 2.0 for now. Regards, Simone -- Simone Rota WEB : http://www.varlock.com Bergamo, Italy MAIL: sip(a)varlock.com

4 3