[Scribus] file format 1.3.3.x and 1.3.4

[Axel Bojer]

listen at thomas-zastrow.de skrev:
> On Tuesday 05 December 2006 10:21, Axel Bojer wrote:
>> listen at thomas-zastrow.de skrev:
>>>> I dont know if I have understood you right, but does mean that when I
>>>> now upgrade from 1.3.5 to 1.3.6 there is a special command for it? Or do
>>>> you simply mean replacing?
>>>> As of now  I am simply using
>>>> ./configure && make && make install
>>>> without removing the old version, and it seems to work fine, so i
>>>> suppose it is. Is this the wanted method?
>>> That's evry simple. Just change the configure-command:
>>>
>>> ./configure --prefix=/directory/where/to/install
>>>
>>> Then Scribus will be installed in the given directory. Removing this
>>> directory also deletes Scribus ;-)
>> Thank you. I suppose thats not what I have, so is there also a good
>> method of removing from the normal procedure (without no prefixes)?
>>
>> I fear not, but anyhow I shall keep this method in mind, can be helpful
>> for instance for cvs-builds :-)
> 
> I think, this depends on your distribution? RPM, apt-get or whatever are 
> normaly able to delete installed packages.

Sure :-)
But unfortunately, last time i checked, there is none for
debian-ish + amd64 :-(

So I installed from the source :-)
Thats not a big problem ... as long as you learn how to do it and don't 
have a fear of comand lines :-)
Just if I had wanted to unistall, then it seems like I would have a problem.

Would be very nice if some remove script also was present for normal 
tar-packages, but, well, I know ... lots of other important things to do 
too.

Wont just apply to those who want to quit using Scribus, just imaging 
wanting to use it just on another machine. (But I know harddisks are big 
these days, one could argument. And for DTP you need that anyway.)

But, well: flexibility is a good thing :-)

It seems like there are lots of other ways of installing to, according 
to the scribus web sites too but, well, I have not digged into it. And 
it seems to be a hazzle to change my method now :-/

Summary: at present: no problems (for me, that is), but I see some 
pitfalls that could have been removed.

Best regards
Axel Bojer