Re: [Fink-devel] 10.3, window managers, and cut & paste issues

[Brian Wilson]

I've tried using it w/ autocutsel, and experience the same problems.

On Wed, 22 Oct 2003, Benjamin Reed wrote:

> Brian Wilson wrote:
>
> > After installing 10.3, I was hoping that a simple recompile of the fink
> > window managers against the Xcode x11-dev package & Xcode gcc would be
> > sufficient for them to work decently.  I was wrong. In 10.2 I was using
> > Xdarwin, but I'm using Apple's X11 package at this moment.  I tried to
> > re-compile fluxbox 0.1.10-2 and blackbox 0.65.0-1 fink packages (and
> > blackbox-0.65.0 and fluxbox 0.1.14 directly from source).  Both packages
> > seem to work (load), but cut and paste functionality is totally broken.
> > Another issue is that the toolbar for both packages (if location is set to
> > TopCenter) is displayed under the Apple menu bar - thus making it
> > impossible to use.  The only window manager I've tried that cut and paste
> > actually work is with apple's quartz-wm. Since I rely on cut and paste so
> > much, I am using quartz-wm till I can figure out what the problem is.
> > I'm not sure if this is an issue with Apple's X11 or if this is something
> > that needs to be patched in the specific window managers.  If anyone has
> > any ideas, I'm all ears.  I'm willing to recompile whatever if you think
> > it will fix the issue.
>
> If you're not using quartz-wm, you should install autocutsel, it
> provides similar functionality of sync'ing the clipboards.
>
> If you don't, then cut-and-paste works like it does in traditional X11,
> and there's basically no synchronization with the apple side of things.
>
>


--
Brian Wilson  <[EMAIL PROTECTED]>  Network Analyst
Communication Technologies, ATD  W: 919.513.3472
North Carolina State University  www.ncstate.net


---
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

[Fink-devel] New built package for review jove

[Blair Zajac]

Hello,

This is my first Fink package and I've built a .info and a .patch
for my favorite Emacs style editor, jove (which launches incredibily
quickly because it's so small).

I'm attaching the two files here for review.

Do I need to add a dependency for fileutils since I'm using
/sw/bin/install to install the files, or should I use /usr/bin/install.

Is it possible to get commit access to the tree to submit these?

After this, I'll try working on getting Amanda into Fink.  Amanda
is at http://www.amanda.org/ and is a network backup utility for
Unix systems.

Best,
Blair

-- 
Blair Zajac <[EMAIL PROTECTED]>
Plots of your system's performance - http://www.orcaware.com/orca/Package: jove
Version: 4.16
Revision: 1
Source: http://www.cs.toronto.edu/pub/moraes/%n/%n-%v.tar.gz
Source-MD5: 38ebd64355a99b0d007aaef17b0d00b1
SourceDirectory: %n
Patch: %f.patch
CompileScript: <<
make JAVEHOME=/sw
<<
InstallScript: <<
make install JOVEHOME=%i
<<
DocFiles: README
Description: A small, fast, portable Emacs clone
DescDetail: <<
Jove (Jonathan's Own Version of Emacs) is a small, fast, portable Emacs clone.
It starts very quickly, which is nice to have for quickly editting a file
where Emacs or XEmacs would take a while to load.
<<
License: Public Domain
Maintainer: Blair Zajac <[EMAIL PROTECTED]>
Homepage: http://www.cs.toronto.edu/~moraes/
diff -ruN jove-orig/Makefile jove/Makefile
--- jove-orig/Makefile  1996-03-18 20:44:33.0 -0800
+++ jove/Makefile   2003-10-23 17:41:36.0 -0700
@@ -24,19 +24,19 @@
 # DFLTSHELL is the default shell invoked by JOVE and TEACHJOVE.
 #
 # If they don't exist, this makefile will try to create the directories
-# LIBDIR and SHAREDIR.  All others must already exist.
+# BINDIR, LIBDIR and SHAREDIR.  All others must already exist.
 
 SHELL = /bin/sh
-TMPDIR = /usr/tmp
-RECDIR = /usr/preserve
+TMPDIR = /sw/var/tmp/jove
+RECDIR = /sw/var/tmp/jove/preserve
 
-JOVEHOME = /usr/local
-SHAREDIR = $(JOVEHOME)/lib/jove
+JOVEHOME = /sw
+SHAREDIR = $(JOVEHOME)/share/jove
 LIBDIR = $(JOVEHOME)/lib/jove
 BINDIR = $(JOVEHOME)/bin
 MANDIR = $(JOVEHOME)/man/man$(MANEXT)
 MANEXT = 1
-DFLTSHELL = /bin/csh
+DFLTSHELL = /bin/tcsh
 
 # The install commands of BSD and System V differ in unpleasant ways:
 # -c: copy (BSD); -c dir: destination directory (SysV)
@@ -46,16 +46,18 @@
 # If you know that /bin/install is the BSD program, you can use it.
 # "cp" will work reasonably well, but be aware that any links continue
 # referencing the old file with new contents.
-
+INSTALL=/sw/bin/install
 INSTALLFLAGS = # -g bin -o root
 
 # to install executable files
-XINSTALL=cp
+#XINSTALL=cp
 #XINSTALL=/usr/ucb/install $(INSTALLFLAGS) -c -m 755 # -s
+XINSTALL=$(INSTALL) $(INSTALLFLAGS) -c -m 755
 
 # to install text files
-TINSTALL=cp
+#TINSTALL=cp
 #TINSTALL=/usr/ucb/install $(INSTALLFLAGS) -c -m 644
+TINSTALL=$(INSTALL) $(INSTALLFLAGS) -c -m 644
 
 # These should all just be right if the above ones are.
 # You will confuse JOVE if you move anything from LIBDIR or SHAREDIR.
@@ -65,6 +67,7 @@
 RECOVER = $(LIBDIR)/recover
 PORTSRV = $(LIBDIR)/portsrv
 JOVERC = $(SHAREDIR)/jove.rc
+JOVELOCALRC = $(SHAREDIR)/jove-local.rc
 TERMSDIR = $(SHAREDIR)
 CMDS.DOC = $(SHAREDIR)/cmds.doc
 TEACH-JOVE = $(SHAREDIR)/teach-jove
@@ -79,7 +82,7 @@
 # compiler, adding -Xa -v will increase compiler checking.
 # On DEC OSF/1, -std1 -O
 
-OPTFLAGS = -O
+OPTFLAGS = -Os
 
 # For making dependencies under BSD systems
 DEPENDFLAG = -M
@@ -164,6 +167,7 @@
 # You can just say 'make SYSDEFS=-Dwhatever' on these systems.
 
 SYSDEFS =
+SYSDEFS = -DBSDPOSIX
 
 # for SCO Xenix, set
 #  MEMFLAGS = -Mle
@@ -179,6 +183,7 @@
 # CC = /opt/SUNWspro/bin/cc
 # For DG AViiON, expect compile errors unless you use the GNU C compiler:
 # CC=gcc
+CC = gcc
 
 # Load invocation of cc.
 # LDCC = purify $(CC)
@@ -329,14 +334,21 @@
 $(TEACH-JOVE) $(CMDS.DOC) $(TERMSDIR)docs \
 $(PORTSRVINST) $(RECOVER) $(JOVE) $(TEACHJOVE) $(MANUALS)
$(TINSTALL) doc/jove.rc $(JOVERC)
+   $(TINSTALL) doc/jove-local.rc $(JOVELOCALRC)
@echo See the README about changes to /etc/rc or /etc/rc.local
@echo so that the system recovers jove files on reboot after a crash
 
+$(BINDIR)::
+   test -d $(BINDIR) || mkdir -p $(BINDIR)
+
 $(LIBDIR)::
-   test -d $(LIBDIR) || mkdir $(LIBDIR)
+   test -d $(LIBDIR) || mkdir -p $(LIBDIR)
+
+$(MANDIR)::
+   test -d $(MANDIR) || mkdir -p $(MANDIR)
 
 $(SHAREDIR)::
-   test -d $(SHAREDIR) || mkdir $(SHAREDIR)
+   test -d $(SHAREDIR) || mkdir -p $(SHAREDIR)
 
 $(TEACH-JOVE): doc/teach-jove
$(TINSTALL) doc/teach-jove $(TEACH-JOVE)
@@ -365,19 +377,19 @@
 $(RECOVER): recover
$(XINSTALL) recover $(RECOVER)
 
-$(JOVE): jjove
+$(JOVE): $(BINDIR) jjove
$(XINSTALL) jjove $(JOVE)
 
 $(TEACHJOVE): teachjove
$(XINSTALL) teachjove $(TEACHJOVE)
 
-$(JOVEM): doc/jove.nr
+$(JOVEM): $(MANDIR) doc/jove.nr
@sed -e 's;;$(TMPDIR);' \
 -e 's;;$(LIBDI

Re: [Fink-devel] New built package for review jove

[Christian Schaffner]

Hi Blair

On Freitag, Oktober 24, 2003, at 02:50  Uhr, Blair Zajac wrote:
This is my first Fink package and I've built a .info and a .patch
for my favorite Emacs style editor, jove (which launches incredibily
quickly because it's so small).
Thanks a lot for this package.

I'm attaching the two files here for review.
May I ask you to add your .info and .patch files to the package  
submission tracker? That will make it easier for fink developers to  
look at it. And we can keep track of the changes. The tracker can be  
found at:



which is linked from the fink homepage.

Do you know that there is also a request open for jove?

This can be closed once you added your package to the tracker.

Do I need to add a dependency for fileutils since I'm using
/sw/bin/install to install the files, or should I use /usr/bin/install.
I always use /usr/bin since then you can be sure that it exists. I  
recommend that for your package too.

Is it possible to get commit access to the tree to submit these?
Normally packagers put their new package into the package submission  
tracker. There they get reviewed and added by one of the developers.  
It's the best way to start packaging since you get feedback.

After this, I'll try working on getting Amanda into Fink.  Amanda
is at http://www.amanda.org/ and is a network backup utility for
Unix systems.
Sounds great!

Cheers, Chris.

PS: Please note the the fink developers are quite busy updating fink  
for 10.3. That's why you might need to wait some time before you  
package gets reviewed.



---
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

Re: [Fink-devel] New fink admin

[rand]

Congrats Peter =)

On 23/10/2003, at 11:03 PM, [EMAIL PROTECTED] 
wrote:

We're pleased to announce that Peter O'Gorman has joined the Fink admin
team, which still includes Max Horn, Ben Reed, and myself.  We've also
set up a mailing address with which you could reach the four of us,
should you need to: [EMAIL PROTECTED] .
  -- Dave Morrison



---
This SF.net email is sponsored by: The SF.net Donation Program.
Do you like what SourceForge.net is doing for the Open
Source Community?  Make a contribution, and help us add new
features and functionality. Click here: http://sourceforge.net/donate/
___
Fink-devel mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/fink-devel

[Fink-devel] The State of Fink

[Benjamin Reed]

In some parts of the world, Panther is already out, so I wanted to give
an update on where things are.  A more formal announcement will come
when we're ready for a "real" release.
How This Will Work
--
First of all, unlike the transition from 10.1 -> 10.2, we will continue
to support the previous Mac OS X release.  It may not be updated as
quickly as the 10.3 tree, but we now at least have the resources in
place to make it reasonable to support both.  It would be nice to have
volunteers from the community to help "backport" 10.3 changes, but that
is something that will probably have to be worked out later.  If you're
interested, drop a line to [EMAIL PROTECTED]
The Transition to GCC 3.3
-
HOWEVER, to ease keeping things in sync between 10.2 and 10.3, our
continued support for 10.2 will *only* be if you are using the gcc 3.3
update, since the differences between gcc3.1 and 3.3 are reasonably
large as far as how porting happens.
If you've been following the fink-devel list, you know that for the past
few months we've been working on a tree dubbed "10.2-gcc3.3", which
currently contains most of the packages in the 10.2 tree, updated to
work with the new compiler.  Even now more packages are getting moved
over each day, and tools have now been written to make it easier to
track changes between the different development trees.
The 10.2-gcc3.3 tree is perfectly usable right now, although a little
incomplete in unstable.  David R. Morrison is working incredibly hard to
finish putting together the first binary distribution for 10.2-gcc3.3,
and it is expected to be coming any day now.
The Transition to Panther
-
The initial target for Panther users will be for you to use the
10.2-gcc3.3 binary distribution.  This tree is binary-compatible with
Panther and should provide a smooth upgrade path to the "real" 10.3 tree.
The 10.3 tree is currently based on a subset of 10.2-gcc3.3, and is,
like it's predecessor, continuously getting updated and is getting
closer to parity with the other trees as time goes on.  There's still
plenty of work to do, but almost all of stable is there, and ready, and
developers are diligently getting packages moved over to the unstable tree.
What You Can Do
---
Please help us test the 10.2-gcc3.3 and 10.3 trees.

10.2:

If you're running 10.2, install the December developer tools if you
haven't already, and then install the August updater.  You can get them
both at the Apple Developer Connection (http://developer.apple.com/).
It does require registration, but is free.
10.3:

If you're already running 10.3, be warned that if you installed fink's
X11 package (instead of a system-xfree86 package), you may need to
force-remove them, and then re-install Apple's X11 (make sure you also
install the X11 SDK from the developer tools!)
Everyone:

Download the 0.15.1 beta of fink here:

http://prdownloads.sourceforge.net/fink/fink-0.15.1-beta.tar.gz?download

...and follow the instructions for the rsync upgrade (which are good
general instructions for upgrading your fink package manager to the beta):
http://fink.sourceforge.net/download/rsync-upgrade.php

The beta will set you up for 10.2-gcc3.3 or 10.3, depending on what OS
version you are running.
*Please* keep in mind that you shouldn't use apt-get or dselect to
install things until we have a binary distribution (or if you do, make 
sure you do "fink update-all" afterwards so that any 10.2-gcc3.3 fixes 
or upgrades get built and installed).  Once the 10.2-gcc3.3 bindist is 
ready, we will make an announcement and it will be safe to use binary 
tools again.

Also keep in mind that for now, 10.2-gcc3.3 and 10.3 are still
considered "beta".  Expect the occasional problem.  Generally, things
are working pretty well, though.
We'll let you know as soon as something official is available.

--
Benjamin Reed a.k.a. Ranger Rick -- http://ranger.befunk.com/
gpg: 6401 D02A A35F 55E9 D7DD  71C5 52EF A366 D3F6 65FE
Standards are the industry's way of codifying obsolescence.




pgp0.pgp
Description: PGP signature