blog'o thnet

To content | To menu | To search

Tag - nanoblogger

Entries feed - Comments feed

Wednesday 16 May 2007

Not the NanoBlogger Port Maintainer Anymore

Well, since I didn't use nanoblogger anymore, I decided to resign as its FreeBSD port maintainer.

And because a bad news doesn't come alone, it seems that nanoblogger will not get much interest in the future. I really enjoy used it for two years now, but because of recent changes with the thnet project, I can't provide help with it anymore.

Thursday 6 July 2006

FreeBSD Port Patch Preview for the Last NanoBlogger's 3.3 RC5

Here is the preview patch for the www/nanoblogger port.

You can apply and install it using the following steps:

# cd /usr/ports/www/nanoblogger && make deinstall
# cd /usr/ports && patch < /tmp/nanoblogger.3.3-rc5.patch
# cd /usr/ports/www/nanoblogger && make install clean clean-depends

Be aware that there are a lot of changes in NanoBlogger itself, so read carefully the NanoBlogger User Manual online documentation and the pkg-message post installation output. After the installation, you can (re)read it using:

# pkg_info -D /var/db/pkg/nanoblogger

Download: nanoblogger.3.3-rc5.patch

Tuesday 9 May 2006

First PR Against the NanoBlogger's Port

Here is the first Problem Report against the NanoBlogger FreeBSD's port. In fact, this was not really a bug nor a big issue, just a misread at the installation time it seems. Read the bug's follow-up for more information... really nothing more to say here.

Friday 3 February 2006

FreeBSD Port Patch Preview for the Last NanoBlogger's 3.3 RC4

Because i will be far from a computer for more than a week (as of today!), i post the preview patch for the www/nanoblogger port.

You can apply and install it using the following steps:

# cd /usr/ports/www/nanoblogger && make deinstall
# cd /usr/ports && patch < /tmp/nanoblogger.patch
# cd /usr/ports/www/nanoblogger && make install clean clean-depends

Be aware that there are a lot of changes in NanoBlogger itself, so read carefully the NanoBlogger User Manual online documentation and the pkg-message post installation output. After the installation, you can (re)read it using:

# pkg_info -D /var/db/pkg/nanoblogger

Download: nanoblogger.patch

Tuesday 1 November 2005

Maintainer of The www/nanoblogger FreeBSD's Port

Just to say that i am the new maintainer of the www/nanoblogger port for the FreeBSD project (for some weeks now). See Problem Report ports/84817 for complete patch and update history.

Here is an excerpt of the PR description:

  • Make portlint(1) happy (portlint -A)
  • Add the files pkg-plist and pkg-message
  • The port conforms a little more to the Porter's Handbook
  • Validate a complete recommended test ordering from porting-testing.html

As a side note, the additional contributors list was not updated to reflect the change of maintainer ship... Not so very important, i think ;-)

Friday 12 August 2005

Adding a New Plugin Using the NanoBlogger Framework

Discussing how to add a copyright notice at each page automatically on the NanoBlogger mailing list, here are the two propositions i can think of.

It can be done by adding directly the copyright notice in the desired template files (i.e. templates/main_index.htm, etc.):

  1. Either writing it in the corresponding files...
    $ diff -u templates/main_index.htm templates/main_index.htm.hardwritten
    --- templates/main_index.htm Wed Jul 6 14:49:05 2005
    +++ templates/main_index.htm.hardwritten Mon Aug 8 13:12:05 2005
    @@ -29,6 +29,10 @@
    $NB_Entries
    </div>
    
    +<div class="side">
    +All content herein © 2006, Your Company, Inc. All right reserved.
    +</div>
    +
    <div id="menu">
    $NB_PageLinks
    </div>
    
  2. Or writing a little plugin to do that... (based on the plugins/fortune.sh code)
    # cat << EOF > ${NB_INST_PATH}/plugins/copyright.sh
    # NanoBlogger Copyright plugin.
    
    # sample code for templates, based off default stylesheet
    #
    # <div class="side">
    # $NB_Copyright
    # </div>
    
    PLUGIN_OUTFILE="$BLOG_DIR/$PARTS_DIR/copyright.$NB_FILETYPE"
    
    nb_msg "generating copyright ..."
    echo '<div class="copyright">' > "$PLUGIN_OUTFILE"
    echo 'All content herein © 2006, Your Company, Inc. All right reserved.' >> "$PLUGIN_OUTFILE"
    echo '</div>' >> "$PLUGIN_OUTFILE"
    NB_Copyright=$(< "$PLUGIN_OUTFILE")
    EOF
    $
    $ diff -u templates/main_index.htm templates/main_index.htm.plugin
    --- templates/main_index.htm Wed Jul 6 14:49:05 2005
    +++ templates/main_index.htm.plugin Mon Aug 8 13:12:29 2005
    @@ -29,6 +29,10 @@
    $NB_Entries
    </div>
    
    +<div class="side">
    +$NB_Copyright
    +</div>
    +
    <div id="menu">
    $NB_PageLinks
    </div>
    

The advantage of the second proposition is the capability to add a general feature using the NanoBlogger framework, and the use of the CSS to modify the new copyright class.

Thursday 11 August 2005

Change the date of a NanoBlogger Post

Here are the complete steps to change the date of a post, to look as if it had been written on the changed date.

  1. Rename the entry's data file name to the desired date
  2. Rename, accordingly to the entry's data file name, the content of the corresponding cat_X.db file in which the entry reside (it seems not to be updated by nb -u all or anything else)
  3. Eventually correct the date in the DATE field of the entry using nb -e #id, correcting the day name too (thanks to the cal(1) utility)

Hum. I think there may be a better way to do this.

Tuesday 19 July 2005

Updating the FreeBSD's Port of NanoBlogger to Release 3.2.3

After deciding to use the NanoBlogger tool to maintain my little space on the web, i had updated the corresponding ports(7) on FreeBSD, currently orphaned at the time of this writing.

The all in one patch produced was committed by Pav Lucistnik, many thanks to him.

As a side note, it may be pointed out that this port include a local FreeBSD port's patch in order to bypass a little bug when creating a new weblog in release greater than 3.2.1 (and so present in 3.2.3). See bug report 1232755 for more information about this issue.