On Fri, Dec 03, 2004 at 06:40:55PM +0100, Philipp Meier wrote:
> On Fri, Dec 03, 2004 at 11:11:58AM -0500, Justin Pryzby wrote:
> > The problem is, that if you have postinst delete the files, they are
> > still registered as belonging to the package. Which is bad, because
> > they wouldn't exist.
On Fri, Dec 03, 2004 at 11:11:58AM -0500, Justin Pryzby wrote:
> The problem is, that if you have postinst delete the files, they are
> still registered as belonging to the package. Which is bad, because
> they wouldn't exist. Donno if there's a way of unregistering files
> (other than parsing /v
rixed <[EMAIL PROTECTED]> wrote:
> As you spoke about the
> debian directory I thought that it would be a mean to have the files
> with the deb without having them installed (like other files on the
> debian directory, none of them beeing copied definitively on the user
> file system).
If you hap
I would further argue that users should be able to see what postinst
did after the fact.
Yes, you are right.
I will install a tarball.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
The problem is, that if you have postinst delete the files, they are
still registered as belonging to the package. Which is bad, because
they wouldn't exist. Donno if there's a way of unregistering files
(other than parsing /var/lib/dpkg/info/$pkg.list).
The only way to use a file which is not "
Frank Küster wrote:
You seem to misunderstand me. If you copy the files to
debian/tmp/usr/share/..., they will also be included in the deb, and
installed on the system - except that you might need to substitute "tmp"
for whatever name you use. How else could you use them in postinst?
hu? Ok, I mi
rixed <[EMAIL PROTECTED]> writes:
> Second Idea was to ln -s ../patches from ./debian, but symlinks must
> be avoided because of CVS.
>
Use something less retarded than CVS?
SCNR, Rotty
--
Andreas Rottmann | [EMAIL PROTECTED] | [EMAIL PROTECTED] | [EMAIL
PROTECTED]
http://yi.org/ro
rixed <[EMAIL PROTECTED]> schrieb:
> Hello, list-men.
>
> Im packaging a program that uses a series of sql patches to upgrade
> from any version to the latest. Those files are located in a 'patches'
> directory in the source tree, but are not installed anywhere by make
> install because they are j
On Thu, Dec 02, 2004 at 03:29:18PM +0100, rixed wrote:
> Hello, list-men.
>
> Im packaging a program that uses a series of sql patches to upgrade from
> any version to the latest. Those files are located in a 'patches'
> directory in the source tree, but are not installed anywhere by make
> ins
Hi,
I would like to use them in the postinst script to upgrade the database
automatically. So, I have to carry those files in the .deb.
Ship them in /usr/share, ask the admin whether she wants the upgrade
performed automatically and if she says no, point to the directory where
they were installe
On Thu, Dec 02, 2004 at 03:29:18PM +0100, rixed wrote:
> I would like to use them in the postinst script to upgrade the database
> automatically. So, I have to carry those files in the .deb.
You don't need to move around those patches in the source package. You
just need to make sure those patche
Hello, list-men.
Im packaging a program that uses a series of sql patches to upgrade from
any version to the latest. Those files are located in a 'patches'
directory in the source tree, but are not installed anywhere by make
install because they are just useful at install, not after.
I would li
12 matches
Mail list logo
