-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

J.A. Magallon wrote:

>
> This remembers me of a problem I had with printerdrake (but sure related
> to samba also). I gave up because I had more urgent things to do, but
> I detected a problem.
>
> I want to add a windows printer via samba. Auto detect did not work.
> I tried to add the printer manually. All works fine until I try to print
> a test page. Printerdrake tried to use something like 'smbprint', but
> I only have samba3. So it is really named 'smbprint3'. I think that
> autodetecting also fails because some like 'smblient' is not there,
> because samba3 provides 'smbclient3'.
>

This may have been that samba3 packages were providing samba at one
stage (ie samba3-client provided samba-client). This was fixed in
3.0-0.alpha21.4mdk. So, if you had a contrib source, but no samba-client
package, if printerdrake installed samba-client, it would probably have
gotten samba3-client.

> So, in short, samba3 and samba need a good amount of 'alternatives'
> to get everything working.

I don't think it is a good idea to have an alpha release of any package
override (via alternatives) stable releases.

And even if it were, I think alternativising the samba3 package would
add too much extra complexity to the spec file (of course, if you want
to take over maintainership of samba3 in contrib and the Mandrake
packaging directories in SAMBA_2_2, SAMBA_3_0 and HEAD in samba cvs, you
can try ...).

> Or make them incompatible and add a few
> symlinks in samba3 package.
>

The whole point of doing all the renames in samba3 is so that you can
install samba3, and be absolutely certain it will not mess with the
stable samba release (for example no possibility for alternatives to
have the wrong version on smbpasswd in use, adding the password entries
to the wrong smbpasswd file etc ...). And, you will notice that you can
change back to not using the 3 suffix by changing one character in the
spec file ... so if you really thing samba3 is ready for production use
on your box, you can edit the spec file and rebuild. No, I don't think
adding a "--with system" option is a good idea yet. Maybe when samba3 is
in beta.

> Can somebody confirm this is really a bug, so I fill an entry in
bugzilla ?
> Or I'm forced to install both samba's ?
>

You should not need both samba's, but if you want samba3-client and you
want to be able to use printerdrake to setup samba printers, you will
need samba-client also. printerdrake should now install samba-client
(not be satisfied with samba3-client).

And I think your bug was dealt with, see bug 2617.

Regards,
Buchan

- --
|--------------Another happy Mandrake Club member--------------|
Buchan Milne                Mechanical Engineer, Network Manager
Cellphone * Work            +27 82 472 2231 * +27 21 8828820x121
Stellenbosch Automotive Engineering         http://www.cae.co.za
GPG Key                   http://ranger.dnsalias.com/bgmilne.asc
1024D/60D204A7 2919 E232 5610 A038 87B1 72D6 AC92 BA50 60D2 04A7
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE+b2nirJK6UGDSBKcRAjMiAJ9jgEu01oVKT8rzoBCXuxFwJEVljACgsgnr
RMjDsjs4TLDh3xFskvnp7Y4=
=KX/T
-----END PGP SIGNATURE-----


Reply via email to