Re: Debian packages containing large files
Hey Basile,
Ah okay let me clarify. This package is not for public consumption
and would not be part of debian distribution. I'm skimming a subset
(percentage based) of our live production database which goes through
some process which generates a debian package in the end. The debian
package is then installed in several different test machines. This
process could happen daily so it doesn't make sense for the test
machines to be filling their local mysql install with the large
mysqldump which takes 6-7 hours. I recently raised the percentage and
noticed that the debian packages will no longer install. I'm mainly
looking for help in explaining why a large file in a debian package
would cause the install process to fail. Thanks!
Best,
Sammy
On Wed, Oct 15, 2008 at 10:42 AM, Basile STARYNKEVITCH
<basile@starynkevitch.net> wrote:
> Sammy Yu wrote:
>>
>> Hi Basile,
>> Thanks for answering me. Yes this package contains mysql data
>> files that are a subset from a very large live database that we would
>> like to duplicate frequently across several other machines.
>> Unfortunately because the mysqldump contains ~30 million statements it
>> takes a very large time to fill so we're using the debian package
>> approach. Would it help, if we somehow cut up table1.idb into smaller
>> files and reconstruct it during post install?
>
>
> I'm not sure to understand. You really should explain in more detail what
> are your intents. What is this huge table? Why do you want to redistribute
> it? What is the license of this data? Is it free & debian compatible?
>
> First, do you intend to make a public deb package, which you hope to fit
> into some future Debian distribution? If yes, please reconsider putting huge
> files in it. If it is just a *.deb file for your private organization, do as
> you please.
>
> Second, are you really intending to package a 30 million row table ? I
> really think that might not be reasonable... Could you explain what is this
> data?
>
> And then, I would suppose that if the mysqldump take a lot of time (how much
> really), there are some options to mysqldump to make it run a bit faster, it
> is not very important. What is more important is the time taken to load the
> database.
>
> But I feel that making a public deb package for a 30 million row table is
> probably the wrong approach.
>
> Please explain more what you are doing.
>
> Regards.
>
> --
> Basile STARYNKEVITCH http://starynkevitch.net/Basile/
> email: basile<at>starynkevitch<dot>net mobile: +33 6 8501 2359
> 8, rue de la Faiencerie, 92340 Bourg La Reine, France
> *** opinions {are only mines, sont seulement les miennes} ***
>
Reply to: