bug-freedink
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Bug-freedink] Re: FreeDink in FreeBSD


From: Sylvain Beucler
Subject: [Bug-freedink] Re: FreeDink in FreeBSD
Date: Sun, 30 Nov 2008 14:08:19 +0100
User-agent: Mutt/1.5.18 (2008-05-17)

Hi,

> Did you look over the patches in the port?  The rm/chmod path fixes in  
> the makefile for freedink-data,

I saw it, thanks for this :) I had partially fixed this in Git but now
it should be good (I need to make a new freedink-data release.)


> and the itlocale change in the dfarc Makefile.in.in

I didn't really understand this one :)

Note that 'Makefile.in.in' is installed by 'intltoolize', so maybe the
patch should go to the intltool project as well.


> I set up the options to default to enabling embedded resources, since it  
> was hinted that's what was preferred, and hardcoded disabling upx since  
> I couldn't figure out why anyone would want to enable it.  :-)

I clarified './configure --help' about embedded resources; indeed
that's the preferred way (so FreeDink can load the default font in all
situations). I only added a way to disable it for distros that enforce
stripping executables after the build process, which removes embedded
resources anyway.

UPX (like --static) is mainly used to generate compact executables for
direct download (e.g. .exe), but it's not very useful for distros
indeed.

Btw, your choice of options is actually the default :)


> Also, I noticed that the main site and the GNU mirror sites have  
> different sets of files.  Haven't gone back and checked if that is fixed  
> yet or not.

freedink.org has some additional binary packages as well as snapshots,
but the source releases are the same.

It's best indeed to use the GNU mirrors directly, so that freedink.org
doesn't use too much bandwidth.


> It was pretty straightforward to do the port though... when I came  
> across FreeDink, I was actually expecting to have to do some porting.  I  
> looked at the code back when it was released and decided that I didn't  
> care enough at the time to do anything about it.  Recently, I decided to  
> go back and slowly pick away at it and discovered that it was already  
> finished.  miwi@ stepped up and fixed my initial porting efforts and  
> checked it in so now I just need to figure out where to subscribe to  
> update announcements.  :-)

Glad that the port was easy - this means FreeDink is truly portable :)

There isn't a dedicated mailing list for release announcements (given
the low traffic of bug-freedink), but I usually post release
announcements at:

http://savannah.gnu.org/news/atom.php?group=freedink
address@hidden
address@hidden

-- 
Sylvain




reply via email to

[Prev in Thread] Current Thread [Next in Thread]