tags of a similar ilk

A post from the Drupal support list requested:

Does anybody know of an existing module which will extract tags from
the body of a post (i.e. a line like "Tags: tag1 tag2 tag3") and pass
them to the taxonomy system to tag that node?

I've had a skim through the Taxonomy related module list on drupal.org
and didn't spot anything...

Cheers,
Dan

Took me longer than I wanted it to take, but at least it's of the minimum quality I find acceptable.

Dan, this one's for you. Download, works for Drupal 5.x

Open Safari on the destination box. You want to use Safari because of the integration with the MacOSX allowing easier installation.

Navigate to http://metissian.com/projects/macosx/subversion/.

Select the binary you want. When in doubt, select the newest one. If you have an older Mac, look for the PowerPC compatible Universal binaries.

The DMG will begin downloading. When completed, you may receive a warning message that your downloaded file contains an executable program. This is what you want, so continue.

Selecting the continue will begin the binary (program) installation. If the installation doesn't automatically continue, and only the DMG opens, double click on the SubversionClient icon (an open box) to continue the SVN installation.

This installation will make the svn commands available on the command line, which means you'll need to use the Terminal application (or X11 + xterm, as I prefer) to access the svn commands. Using the Terminal application will open a shell (bash, csh, tcsh, depending on your configuration), which accepts command line input commands. In order for this to be effective, however, your shell needs to know where the svn commands are. And for this, you may need to adjust the PATH variable.

Hi!

You're probably looking for the details of the whole Gallery PostNuke to Drupal conversion (including some of the pain Bharat went through with it). I'll get that written up in the next day or two. If you're a PostNuke person looking to transistion to Drupal, well, yeah, I'll get those details up, too.

You can contact me in the mean time, if you have specific Drupal/PostNuke/Gallery questions that I can answer.

With CVS, ignoring files in a local checkout is easy. You add the file name to the .cvsignore file in the directory the file is located in. When a cvs command was issued in that directory, the files listed in the .cvsignore would be, well, ignored.

% cat .cvsignore
config.inc.local
.cvsignore

Note that .cvsignore is listed in the .cvsignore file as well. Otherwise, the file would list each time a cvs update was made:

% cvs up
? .cvsignore
U config.inc

So, ignoring files is pretty easy with CVS, right?

What happens when everyone who has a local checkout wants to ignore the same files (a common scenario when development processes create temporary, intermediate files)?

Right, each developer needs to create his own .cvsignore file in each local checkout.

Subversion handles the process of ignoring files in a local checkout differently.

Instead of creating a local ignore file, you can set an "ignore property" in a directory for a specific file or subdirectory. This property is set in the repository and is applied to all local checkouts. With this strategy, all checkouts will behave the same way (i.e. all local checkouts on the same revision will ignore the same files and subdirectories).

This is goodness. So how are these set?

svn propset svn:ignore file directory

Here, we are setting the property svn:ignore on the file file in the directory directory. The file can actually be another directory:

svn propset svn:ignore subdirectory directory

So, let's say you have a logs subdirectory in the current directory that you want to ignore:

% svn status
?      logs

Your ignore command would be:

% svn propset svn:ignore logs .
property 'svn:ignore' set on '.'

Now, when you first set this value, you've modified the directory information in the local checkout. You'll need to commit this structure change back into the repository for the changes to be seen in other checkouts:

% svn st
 M     .
% svn ci -m "Ignore the logs subdirectory." .
Sending        .

Committed revision 12207.

As mentioned above, you can also ignore files in and subdirectories of directories beneath the current directory:

% svn st
?      devt/logs
% svn setprop svn:ignore logs devt
property 'svn:ignore' set on 'devt'
% svn st
 M     devt
% svn ci -m "Ignore the logs subdirectory" devt
Sending        inc

Committed revision 12208.

Now when you do a status listing on the local checkout, your ignore files will be properly ignored:

% svn st
%