TRAMP for emacs development has continued since the 20020411 build that is currently in portage. The most recent release, available at http://savannah.nongnu.org/projects/tramp, is 2.0.34. The syntax for remote file access has changed since this build, but is more consistent with EFS/standard URLs. Emacs 21.4 is going to include this TRAMP as part of the base, so this is not a priority, but would be nice :)
Created attachment 12901 [details] 2.0.34 ebuild TRAMP install is much simplified since 20020411, requiring little more than ./configure make make install I successfully installed this from PORTDIR_OVERLAY with export SANDBOX_DISABLED=1; emerge \ /usr/local/portage/app-emacs/tramp/tramp-2.0.34.ebuild This is my first ebuild, so I don't know if this is at all acceptable, but, as I said it worked for me.
Created attachment 12902 [details] My changelog
Created attachment 12903 [details] files/digest-tramp-2.0.34
Thanks for this work. Unfortunately, tramp is now at 2.0.35 :-( I tried your ebuild and got the following errors ... ------------------------------------ .... >>> Install tramp-2.0.34 into /var/tmp/portage/tramp-2.0.34/image/ category app-emacs make[1]: Entering directory `/var/tmp/portage/tramp-2.0.34/work/tramp-2.0.34/lisp' install -m644 tramp-efs.el tramp-ftp.el tramp-smb.el tramp-util.el tramp-uu.el tramp-vc.el tramp.el trampcache.el trampver.el tramp-efs.elc tramp-ftp.elc tramp-smb.elc tramp-util.elc tramp-uu.elc tramp-vc.elc tramp.elc trampcache.elc trampver.elc /usr/share/emacs/site-lisp ACCESS DENIED open_wr: /usr/share/emacs/site-lisp/tramp-efs.el install: cannot create regular file `/usr/share/emacs/site-lisp/tramp-efs.el': Permission denied --------------------------- then lots more permission denied errors too. I'm going to install the old-fashioned way, which is a shame, as I like portage... I just don't understand it.
Comment on attachment 12901 [details] 2.0.34 ebuild As was pointed out, this doesn't work ('cuz I'm an idiot). Besides, there's a new version out.
Created attachment 14729 [details] tramp-2.0.35.ebuild This ebuild may actually work.
Created attachment 14730 [details] ChangeLog for 2.0.35
Created attachment 14731 [details] Digest file for 2.0.35
I'll look into it. First of all, there comes newer version (2.0.36) available ;-) Will you make a ebuild for it? Your ebuild (2.0.35) seemss pretty good, rather it looks you know how to create one :-) However, I should point out that it doesn't install info file correctly. (1) It tries to install info file to ${D}/usr/share/info but at the installation time ${D}/usr/share/info hasn't yet been created, so it ends up with installing info file as '${D}/usr/share/info'. An easy workaround is to put "dodir /usr/share/info" before "make install ... || die". (2) However, adding "dodir /usr/share/info" doesn't simply solve the problem. Though it creates ${D}/usr/share/info/tramp during the installation process, the filename of info file isn't appropriate. It should be 'tramp-info' rather than 'tramp', so you have to rename the info filename. I leave it to you how to fix it. In addtion to the info issue, it will not install HTML files, so it's better to add "dohtml texi/*.html" in src_install(). ChangeLog.orig doesn't seem to exist, so you can delete it from dodoc. Please let me know when you've done these changes and post your ebuild here. The ebuild file alone is perfectly fine (i.e. you needn't attach digest; we can make it automatically). We also create ChangeLog entry by ourselves, so in most cases you don't have to write one. (btw, in this case your comment in ChangeLog will help users know a problem they may come across, so it is very good habit to note sucn a problem)
Created attachment 15351 [details] tramp-2.0.36.ebuild Hopefully this does this trick. Don't know if I'd go so far as to say I know "how to create one" (did you see the one for 2.0.34?). Let me know if I missed anything with this. I couldn't figure out a way to supercede the previous version, which used a YYYYMMDD version number rather than the current VERSION.SUBVERSION system. Is there any way to do that?
Okay, your ebuild looks quite good. I'll commit it later. src_unpack() in your ebuild is not necessary because portage unpacks every source automatically (as the previous version does). As for versioning, I don't know how to supercede the previous version. If we create an ebuild as VERSION.YYYYMMDD.ebuild it will be supercedable, but there isn't much to do for source snapshot VERSION.ebuild. I told portage development team about the problem few days ago, so they may or may not provide us some solution to it in the future.
Thanks for the contribution chris, it's now in CVS.
